samba - Feb 2025 - How to safely rejoin an upgraded linux domain member?

The leave / join process of a samba server is straight forward and should give
no grief.

Build the new server, sync the data with rsync -AXavz (will preserve all xattr)
from old to new (with old server running and in ops) also sync the smb.conf
file. I understand shares will be equal if not update smb.conf. On transition
day advise of downtime, do a final rsync (should be quick).

Stop samba, remove smb.conf and power off old server.

Join the new server with same name. Users should not notice the change.
On 27 Feb 2025 at 15:46 +0000, Jakob Curdes via samba <samba at
lists.samba.org>, wrote:
>
> Hi, we have to upgrade one large server, which is a domain *member* of
> an AD domain driven by two samba4 DCs, to the newest Ubuntu version, and
> due to the size we cannot just to it in one short downtime.
> So I created a clone, deactivated all samba services and did the update.
> It currently has a different name, and has not yet been rejoined to the
> domain. What is a safe way to replace the old with the new server, using
> the same name (as otherwise we need to rename all fileshares mounted on
> clients)? I would think I leave the domain with the old server and then
> join the domain with the new one under the same name. OR does that lead
> to problems?
>
>
> Best regards, Jakob
>
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: lists.samba.org/mailman/options/samba

Typo: rsync -AXav (no z) unless bandwidth is a problem.
On 27 Feb 2025 at 17:05 +0000, Luis Peromarta via samba <samba at
lists.samba.org>, wrote:
> The leave / join process of a samba server is straight forward and should
give no grief.
>
> Build the new server, sync the data with rsync -AXavz (will preserve all
xattr) from old to new (with old server running and in ops) also sync the
smb.conf file. I understand shares will be equal if not update smb.conf. On
transition day advise of downtime, do a final rsync (should be quick).
>
> Stop samba, remove smb.conf and power off old server.
>
> Join the new server with same name. Users should not notice the change.
> On 27 Feb 2025 at 15:46 +0000, Jakob Curdes via samba <samba at
lists.samba.org>, wrote:
> >
> > Hi, we have to upgrade one large server, which is a domain *member* of
> > an AD domain driven by two samba4 DCs, to the newest Ubuntu version,
and
> > due to the size we cannot just to it in one short downtime.
> > So I created a clone, deactivated all samba services and did the
update.
> > It currently has a different name, and has not yet been rejoined to
the
> > domain. What is a safe way to replace the old with the new server,
using
> > the same name (as otherwise we need to rename all fileshares mounted
on
> > clients)? I would think I leave the domain with the old server and
then
> > join the domain with the new one under the same name. OR does that
lead
> > to problems?
> >
> >
> > Best regards, Jakob
> >
> >
> >
> > --
> > To unsubscribe from this list go to the following URL and read the
> > instructions: lists.samba.org/mailman/options/samba
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: https://lists.samba.org/mailman/options/samba

On Thu, 27 Feb 2025 17:04:18 +0000
Luis Peromarta via samba <samba at lists.samba.org> wrote:
> The leave / join process of a samba server is straight forward and
> should give no grief.
> 
> Build the new server, sync the data with rsync -AXavz (will preserve
> all xattr) from old to new (with old server running and in ops) also
> sync the smb.conf file. I understand shares will be equal if not
> update smb.conf. On transition day advise of downtime, do a final
> rsync (should be quick).
> 
> Stop samba, remove smb.conf and power off old server.
> 
> Join the new server with same name. Users should not notice the
I would think the only possible way of anything noticing is if the
computers SID is used in a search. Even though everything is the same,
leaving the domain and joining again will mean the computer being
treated as a new machine with a new SID.

Rowland