samba - Jun 2024 - 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 ?

Am 06.06.24 um 19:51 schrieb Stefan G. Weichinger via
samba:
> 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.
will do more or less

But not sync "/var/lib/samba", right?
>> 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.
Could I join the domain with another name and IP now ... to be able to 
test things (introducing btrfs snaphots this time) with all AD-features, 
but on a "test name"? And then leave the domain, change FQDN/IP and
rejoin?

I want to avoid any issues coming from doing something wrong NOW. That 
server should be productive for some years from now (sure).