[Samba] moving DC to new hardware
L.P.H. van Belle
belle at bazuin.nl
Wed Feb 3 10:40:06 UTC 2021
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.
> -----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
More information about the samba