Hello Stefan, 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 -----Urspr?ngliche Nachricht----- 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 wrote:> 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 > DBs. > > 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 -- 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 instructions: https://lists.samba.org/mailman/options/samba
Am 03.02.21 um 10:46 schrieb Joachim Lindenberg via samba:> Hello Stefan, 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...I agree and understand. Small company (~20 ppl) there so their budget is limited. That plays into searching for the easiest and shortest path now (also in terms of money ...). Adding DC3: elegant, sure. I just fear the complications around that, all the "new hostname", "sync SYSVOL" etc I tend to clone the disks and move over ... in a maintenance window.
Down all services on the older server. tar.gz the full filesystem install it the minimals as possible on the new server. unzip the tar over the new server. fix, if needed, the MAC adres linked to network interface. and you should be good to go. Greetz, Louis> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Stefan G. > Weichinger via samba > Verzonden: woensdag 3 februari 2021 10:58 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] moving DC to new hardware > > Am 03.02.21 um 10:46 schrieb Joachim Lindenberg via samba: > > Hello Stefan, 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... > > I agree and understand. > > Small company (~20 ppl) there so their budget is limited. That plays > into searching for the easiest and shortest path now (also in terms of > money ...). > > Adding DC3: elegant, sure. I just fear the complications around that, > all the "new hostname", "sync SYSVOL" etc > > I tend to clone the disks and move over ... in a maintenance window.yes, thats about the same as i suggested. if you search for rsync in samba list, there are a few more posts on that. I recently moved my mailserver from broken hardware to other server. i only fixed the mac adress link in udev Greetz, Louis