similar to: Restore Samba from backup

Hi Rowland, On Sun, 26 May 2019 at 19:54, Rowland penny via samba <samba at lists.samba.org> wrote: > 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

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,

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, I'm running > into issues that have kept me for hours on this already. > >

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 > >

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.

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

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

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 Viktor, In 4.10.0, the fix for https://bugzilla.samba.org/show_bug.cgi?id=13760 will take effect when the samba process first starts. In theory, if you take a backup after this, that backup database should no longer have bug 13760 in it. It seems like what you're seeing might be a different problem. If samba_dnsupdate isn't working, then DNS may well not work. And if DNS isn't

I could really use some support with this. I understand it's always possible to just restore from a backup but the more interesting question is if something can be done with the data at hand. Basically, I'm trying to understand how it's possible that a dbcheck shows no errors, an ldbsearch is successful, and yet it's not possible to start the AD properly. What else is there that

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

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

In our organization, we tested the crap out of different backup methods before rolling out AD. Here's what we tested and worked: 1. All DCs are VMs, on at least two different VM hosts (either running Virtualbox, Xen or KVM) 2. All domains have at least two DCs 3. We shutdown (nicely) DC2, and backup the disk image and machine definition file to our backup server 4. We turn on DC2 again.

On 17.11.2015 18:05, Rowland Penny wrote: > 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

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

Hi All! I would be grateful for clarification of my doubts about backups and restoration of the AD environment. What is the best strategy for backing up and restoring a Samba AD domain in the following scenarios: * server1 - active directory service (7 FSMO roles) * server2 - active directory service + Samba file server The considered disaster recovery scenarios are: - Corruption of the AD

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 Trojanovic <viktor at troja.ch> wrote: > > > > > On Sun, 10 Feb 2019 at 17:42, Rowland Penny via samba > > >

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 17:19, mathias dufresne wrote: > Here are my (little) view regarding shares accesses. I

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