I?d get the new server ready, sync all data including xattrs & ACLs with rsync -AXav You probably use AD or RID. Just use the same idmapping on the new server. Probably just copy old smb.conf to new machine. When all is rsynced just remove the old server from the AD, turn off, assign name and IP address to new server. Join domain. That should do. If all goes very wrong you can just power on your old server , and rejoin. Things should be as before. Regards. LP On 31 May 2024 at 12:29 +0100, Stefan G. Weichinger via samba <samba at lists.samba.org>, wrote:> > forgive me the FAQ ... > > I run a samba-4.19.6-domain-member-server on Debian 12.5 and have to > move that to a new hardware. > > I should keep the name of the server, and the IP ... and the downtime > should be short. > > Is there a recommended procedure for doing that? > > thanks in advance, Stefan > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba
Stefan G. Weichinger
2024-Jun-06 17:51 UTC
[Samba] move domain member server to new hardware
Am 31.05.24 um 14:38 schrieb Luis Peromarta via samba:> I?d get the new server ready, sync all data including xattrs & ACLs with rsync -AXav > > You probably use AD or RID. Just use the same idmapping on the new server. Probably just copy old smb.conf to new machine. > > When all is rsynced just remove the old server from the AD, turn off, assign name and IP address to new server. Join domain. That should do. > > If all goes very wrong you can just power on your old server , and rejoin. Things should be as before.thank you, sounds not that scary ;-) what about the fqdn in linux itself? I can't change that hostname on the old server until I deactivate it. It should stay some kind of fallback server (with another fqdn and IP) later. I am using ansible (with the debops roles) to configure the servers, I will see if I can easily reconfigure the name between turning off the old hardware and enabling the services on the new hardware. Or just don't care that much about the linux FQDN and set a different server name in smb.conf ?