[Samba] moving DC to new hardware
samba at lindenberg.one
Wed Feb 3 09:46:19 UTC 2021
Ultimately the question is, what safety belt you want in case your copy operation fails for whatever reason. Once you fired up DC_new, you should not fire up DC_old again, and if DC_new doesn´t work properly, then essentially DC_old and DC_new are dead at least for some time in which there is no resilience anymore. Therefore joining a third DC as Andrew suggests is definitely the better approach.
I´d definitely recommend virtualization to ease your future life...
Best Regards, Joachim
Von: samba <samba-bounces at lists.samba.org> Im Auftrag von Andrew Bartlett via samba
Gesendet: Wednesday, 3 February 2021 10:38
An: Stefan G. Weichinger <lists at xunil.at>; samba <samba at lists.samba.org>
Betreff: Re: [Samba] moving DC to new hardware
On Wed, 2021-02-03 at 10:33 +0100, Stefan G. Weichinger via samba
> I start to google and look for the best way to move one of two
> Samba-4.12.x DCs to new hardware.
> I assume I could shutdown "DC_old", then copy/dd the filesystems to
> the new SSDs in the new server and (try to) boot it up there again.
> Sounds easy.
> The more complicated way might be setting up "DC_new" (ok, keep the
> hostname from "DC_old") fresh, cp over the various config files and
> I have a DC2 that won't be touched in the process. That one should
> keep my AD online.
> DC_old is a up to date Debian server, it should just be transferred to
> new hardware.
> I want to avoid any unnecessary steps and issues here.
Both should work but most folks take this as a time to refresh the host OS and so just join the new hardware with a new OS as a third DC, making sure everything is working then demoting the old hardware.
Andrew Bartlett (he/him) https://samba.org/~abartlet/
Samba Team Member (since 2001) https://samba.org
Samba Team Lead, Catalyst IT https://catalyst.net.nz/services/samba
To unsubscribe from this list go to the following URL and read the
More information about the samba