[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: upgrade procedure

To: BÖSCH Christian <boesch@fhv.at>, <openldap-technical@openldap.org>
Subject: RE: upgrade procedure
From: Jason Trupp <jtrupp@symas.com>
Date: Tue, 6 Nov 2018 07:35:02 -0600 (CST)
Content-language: en-us
In-reply-to: <60D0A221-FF72-4A8D-81D7-5E1F526BED62@fhv.at>
References: <60D0A221-FF72-4A8D-81D7-5E1F526BED62@fhv.at>
Thread-index: AQMtyKZjs4IQAnrdy8PejJTTpo7u2qKQGDUA
Thread-topic: upgrade procedure

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

Follow-Ups:
- RE: upgrade procedure
  - From: Quanah Gibson-Mount <quanah@symas.com>

References:
- upgrade procedure
  - From: BÖSCH Christian <boesch@fhv.at>

Prev by Date: upgrade procedure
Next by Date: RE: upgrade procedure
Index(es):
- Chronological
- Thread