Christian,

There is an alert warning for MDB users who have multival-hi and multival-lo configured. If you using these then a database reload needs to be part of your upgrade plan. Otherwise, take one master down, perform a backup using slapcat, update the software and bring it back up. Wait for replication to catch up. Then repeat the process on the second master. You should be able to avoid downtime and dataloss.

If you're going to the trouble to upgrade, why not use 2.4.46 which has several improvements and fixes over 2.4.45. Just a thought.

Warmest regards, Jason Trupp Symas Corporation (855) LDAP-GUY

--On Tuesday, November 06, 2018 10:00 AM +0000 BÖSCH Christian boesch@fhv.at wrote:

Hi,

What would be the best approach to upgrade a multimaster setup?

Is it possible to stop node#1 (version 2.4.43), do the upgrade to 2.4.45 and then start the node again, let it replicate (does the version mismatch matter?), and afterwards do the same with node#2?

Generally for upgrading OpenLDAP, you simply drop the new binary in place and restart. If you use back-bdb/hdb and the underlying version of BerkeleyDB has changed, then you will have to slapcat, upgrade the binary, slapadd.

Regards, Quanah

--

Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com