similar to: AD Backup Best Practice

See comments inline. On Sun, 10 Feb 2019 at 16:33, Rowland Penny via samba <samba at lists.samba.org> wrote: > On Sun, 10 Feb 2019 14:13:27 +0100 > Viktor Trojanovic via samba <samba at lists.samba.org> wrote: > > > I'm currently reviewing my own backup strategy for Samba and I > > realize it is not in line with best practices provided in the Wiki. ( >

Hi, Thanks for the feedback. I appreciate the whole backup/restore process is more complicated than it needs to be (especially when you're trying to restore in a panic). I've explained below the technical reasons why the backup/restore has these current limitations. The short answer is: - We spent a huge amount of time implementing the current backup/restore tool. Unfortunately, we just

A good practice is to have at least 2 DCs in a domain. If one crashes, you can reinstall one from scratch, join it to the domain and it will synchronize with the safe one. And your services should not stop in the meantime. That doesn’t prevent us from setting up backups, but that reduce risks a lot. :-) G. > Le 10 févr. 2019 à 17:07, Viktor Trojanovic via samba <samba at

On Sun, 10 Feb 2019 14:13:27 +0100 Viktor Trojanovic via samba <samba at lists.samba.org> wrote: > I'm currently reviewing my own backup strategy for Samba and I > realize it is not in line with best practices provided in the Wiki. ( > https://wiki.samba.org/index.php/Back_up_and_Restoring_a_Samba_AD_DC) > Said best practices, however, seem a bit like a nightmare to me. >

I am cc'ing Tim Beale on this, he wrote the wikipage and, I think, most of the backup & restore code. On Sun, 10 Feb 2019 17:07:55 +0100 Viktor Trojanovic <viktor at troja.ch> wrote: > See comments inline. > > On Sun, 10 Feb 2019 at 16:33, Rowland Penny via samba > <samba at lists.samba.org> wrote: > > > On Sun, 10 Feb 2019 14:13:27 +0100 > >

On 26/05/2019 18:28, Viktor Trojanovic via samba wrote: > Small update: I added "lo" to the interfaces in smb.conf, now smbclient > works also on localhost. But both the other problems remain as described > for now. > > On Sun, 26 May 2019 at 19:17, Viktor Trojanovic <viktor at troja.ch> wrote: > >> I just did a restore of a backed up Samba DC and as feared,

On Sun, 10 Feb 2019 at 20:23, Rowland Penny via samba <samba at lists.samba.org> wrote: > On Sun, 10 Feb 2019 20:11:02 +0100 > Viktor Trojanovic <viktor at troja.ch> wrote: > > > On Sun, 10 Feb 2019 at 19:52, Rowland Penny via samba > > <samba at lists.samba.org> wrote: > > > > > On Sun, 10 Feb 2019 19:33:17 +0100 > > > Viktor

I just did a restore of a backed up Samba DC and as feared, I'm running into issues that have kept me for hours on this already. Everything seems fine at first sight. The daemon (samba-ad-dc, 4.10, on Ubuntu Bionic) starts properly and without error messages in any log, even with increased level 3. Most of the typical testing and troubleshooting commands give the correct output.

On Sun, 10 Feb 2019 at 19:52, Rowland Penny via samba <samba at lists.samba.org> wrote: > On Sun, 10 Feb 2019 19:33:17 +0100 > Viktor Trojanovic <viktor at troja.ch> wrote: > > > On Sun, 10 Feb 2019 at 17:42, Rowland Penny via samba > > <samba at lists.samba.org> wrote: > > > > > > > > > > > The problem is that a Samba AD DC

On Sun, 10 Feb 2019 at 17:42, Rowland Penny via samba <samba at lists.samba.org> wrote: > > > The problem is that a Samba AD DC is constantly in flux, that is, it > changes constantly, if your 'snapshot' can guarantee it is correct, > then I see no problem, but you would only really know when you tried > to restore it. > > >With regards to information

> On 14 Mar 2019, at 20:23, Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Thu, 14 Mar 2019 20:12:25 +0100 > Viktor Trojanovic via samba <samba at lists.samba.org> wrote: > >> Hi Greg, >> >> I'm assuming the reason for this was that Robert's answer pretty much >> covered it. Most backup tools still in development, and

Let me guess. You accessing your server like : \\servername\netlogon of \\servername\sysvol Well thats protected by windows these these days. Try with \\servername.domain.tld\netlogon or \\servername.domain.tld\sysvol Does that work? Yes, There is a whole chaper of this on the list somewhere.. Best is to read howto override this. https://adsecurity.org/?p=1405 and for you

Here are my (little) view regarding shares accesses. I write that to clarify things. And it could really be of-topic as Louis seems to have gave solution. There are 2 levels of authorisation for accessing shares: the share level and FS level. For Sysvol I would keep everyone or replace it by "authenticated users" in paranoid mode as the latter refuse non-authenticated users. They are

I was experiencing problems with Group Policy Objects. The Windows Event Viewer spits out so many different errors, most of them less than helpful, so Iwas seeking help here with some of those messages. In the end, and after many hours and even days of researching this problem, I seem to have pin-pointed the main issue to some simple permission irregularities that I don't know how to

Hi Greg, I'm assuming the reason for this was that Robert's answer pretty much covered it. Most backup tools still in development, and I'm including rsync here, do support extended attributes, so you're covered when it comes to ACL. The main question becomes if you need the backup itself to be encrypted, and if yes you might want to look at alternatives to rsync. I heard good

On 16.11.2015 14:44, Rowland Penny wrote: > On 16/11/15 13:25, Ole Traupe wrote: >> >> >> Am 16.11.2015 um 14:06 schrieb Viktor Trojanovic: >>> >>> >>> On 16.11.2015 13:48, Viktor Trojanovic wrote: >>>> See replies below >>>> >>>> On 16.11.2015 12:39, Rowland Penny wrote: >>>>> On 16/11/15 11:19,

I have an AD with 1 Samba DC and 5 Windows 10 clients. The DC and the clients all have a fixed IPv4 address. In the windows event viewer, I constantly see the following warning: Event 8019, DNS Client Events ------------------------------------------ The system failed to register host (A or AAA) resource records (RRs) for network adapter with settings: Adapter Name: {someGUID} Host Name:

On 25.01.2016 14:13, Viktor Trojanovic wrote: > Hi Ole, > > Unless you want to add functionality that is new since 1511, I don't > think that's necessary. I have already added a Win10 machine to a domain, where only Win7 clients were joined before that. I have managed this domain from Win7 only, so far. Therefore I believe that e.g. the Windows Update policy is not fit for

Viktor, thanks again! Now that I did this (added the Win10 1511 ADMX files to the central store), I probably will have to recreate the policies that will be applied to Win10 machines, right? Ole On 21.01.2016 17:16, Viktor Trojanovic wrote: > Hi Ole, > > I've been using Samba with Win10 clients for a while now, so I'm happy > to share some of my findings. > > See

On 17/11/15 16:57, Viktor Trojanovic wrote: > Hi Mathias, > > Thanks for replying. It seems you're describing the situation on the > AD DC. Computer and user mode access to my DC works fine and without > any issues but I can't access the shares of my *member* server *in > computer mode*. In user mode, it all works just fine. > > Viktor > > On 17.11.2015