[Samba] Failover DC did not work when Main DC failed

MORILLO Jordi j.morillo at educationetformation.fr
Wed Jan 29 16:27:31 UTC 2020

Have you set on your clients DNS1 -> DC3 and DNS2 -> DC4 ?
"main DC" and "failover DC" are not Active Directory compliant terms ;-)
There is no master or secondary. Only DC's... some of them could have FSMO roles or could be "head bridge" in a star réplication configuration. If not, they are all egal :-)

-----Message d'origine-----
De : samba <samba-bounces at lists.samba.org> De la part de Paul Littlefield via samba
Envoyé : mercredi 29 janvier 2020 16:56
À : samba at lists.samba.org
Objet : [Samba] Failover DC did not work when Main DC failed

We have a main DC (dc3) and failover DC (dc4) running in a Proxmox virtual environment.

Both DCs are replicating happily and have been running for over a year with no problems.

This morning, our main DC (running as a VM) was backed up and then restarted but Ubuntu did not start the 'samba-ad-dc' service on boot.

The failover DC was up and running at the time, but staff could not log in on their workstations and the QNAP file server (which is domain joined) was also not happy.

The fix was to reboot and everything was well again.

Lesson learned... check port 135 as well as port 22 on Nagios, and check that the failover DC works!

My question... why didn't the failover DC do its job?



To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

More information about the samba mailing list