On 08Mar23 17:48+0100, Meike Stone wrote:
> Oh my god, almost a year has passed - now finally our department wants
> to migrate to the latest version 2.5.14. I'm responsible for the
> Master LDAP-Server, but there are a few ro-replicas in other
> departments where I'm not responsible - and I have no access.

That's an unfortunate condition. 

> Is it possible to migrate the master server to the new version and
> update the replicas (running 2.4.59) later, independent from the
> master (migration)? Are there any problems to be expected?

I can tell from my recent experiences:
I upgraded our infrastructure from 2.4.48 to 2.6.3 and had syncrepl (no 
delta sync) running between different slapd versions; where 
sync-consumers where first upgraded to 2.6.3 and sync-providers remained 
on 2.4.48. Upgrade was done by synching a fresh copy of the DB.
After that, the two providers (mirror pair) went to 2.6.3 in the same 
manner.

I tested all this in advance before doing the stunt on production. Went 
all fine here with zero downtime and slapcat/add was not used.

back-mdb was already in place, but maybe this procedure might give you 
an idea when thinking about upgrading your systems. And just to repeat 
that previous and important paragraph: I tested everthing in advance so 
I felt confident while doing it during production. I suggest you do 
testing as well. 


HIH,
-- 
Bastian Tweddell            Juelich Supercomputing Centre

-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Stefan Müller
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Dr. Ir. Pieter Jansens,
Prof. Dr. Astrid Lambrecht, Prof. Dr. Frauke Melchior
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to