[389-users] Re: Upgrading with replication

On 18/12/2025 14:03, Pierre Rogier wrote:
> Hi,
> You can upgrade both replicas at different time (and make sure that
> everything work as expected before upgrading the second replica to
> ensure service continuity)
>
> Usually a simple dnf upgrade is enough but 3.1.3 requires some manual steps
> because bdb databases needs to be mitigated to lmdb (as explained in
> https://www.port389.org/docs/389ds/howto/howto-migrate-bdb-to-lmdb.html

Looks like if you create your instance on RHEL10 or a rebuild like Rocky
then you get an lmdb backed by default

[root@ldap1 ~]# dsconf ldap1 backend config get | grep
nsslapd-backend-implement
nsslapd-backend-implement: mdb

Upgrade went smoothly, looks like a payoff from migrating from NIS so
late in the day :-)

For the avoidance of doubt we never used NIS for authentication, only
accounting and authorization. Authentication has always and remains
handled by the university AD using Kerberos.


JAB.

--
Jonathan A. Buzzard Tel: +44141-5483420
HPC System Administrator, ARCHIE-WeSt.
University of Strathclyde, John Anderson Building, Glasgow. G4 0NG
--
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue