[Samba] Need to upgrade to latest samba -> Any caveats?"

Kees van Vloten keesvanvloten at gmail.com
Tue Aug 27 14:19:06 UTC 2024


On 27-08-2024 15:28, Marco Shmerykowsky PE via samba wrote:
>
>
> On 8/26/2024 11:20 AM, Rowland Penny via samba wrote:
>> On Mon, 26 Aug 2024 11:08:32 -0400
>> Marco Shmerykowsky PE via samba <samba at lists.samba.org> wrote:
>>
>>> both
>>>
>>
>> In a situation like this, I would create new DCs and then demote and
>> remove the old ones.
>
> When I went from Buster to Bullseye & did a large leap in Samba 
> versions, I upgraded in place.  Aside from having to install some
> missed packages, it went fairly smoothly.
>
> If I understand you correctly, you're suggesting setting up an
> entirely new physical machine.
A (privileged) container or a VM will do the trick.
>
> Did I just lucky with my past upgrade?

Not really, it is supposed to work.

However, with an in-place package upgrade the rollback is much more work 
than with a separate machine.

Another advantage is that for a separate machine only the protocol on 
the wire has to be compatible to succeed, whereas with a package upgrade 
you are talking about lots of local files and databases.

- Kees

>
>> The Unix domain members could be treated in the same way, but I suppose
>> you will want to retain the original hostnames & ipaddresses. Before you
>> do anything, I would back up any data, permissions and the smb.conf,
>> that is all you need to recreate a Unix domain member. At this point
>> you could attempt the dist-upgrade (having removed the backports line),
>> it should work, but if it doesn't, you have the backup to fall back on
>> ;-)
>>
>> Rowland
>>
>
>



More information about the samba mailing list