keep it simple. first, theres no need of upgrading your bdb. 4.2.52 has the longest history to be stable. for bdb versions, see: http://www.openldap.org/lists/openldap-technical/200807/msg00138.html

if you want to upgrade your slapds und bdb, you should dump first your db files the traditional way (slapcat), there should be no need to "convert" your data when re-import them with slapadd. http://www.openldap.org/lists/openldap-software/200802/msg00289.html you should not use any bdb-internal upgrading-tools.

next: easiest way to upgrade surely will be to stop all slapds.

as mentioned above, before any upgrade, stop all slapds if possible (or at least one), then slapcat > dbdump.ldif on this master (e.g. master1). remove all old db-files except DB_CONFIG on all masters (if they are down) upgrade to 2.4.12 and the bdb you want (except 4.3) on all masters (if they are down) slapadd the ldif on master1, start this one first , then your other masters, they will fetch your dit from the first master, if your replication-config is setup correctly.

if you have to keep the system up (or just have a small downtime) then stop master1, slapcat, upgrade slapd and bdb, slapadd. stop the other masters, and then start master1. on the other masters just upgrade slapd and bdb and remove the old db-files, they should be synced from master1 when theyre slapds are restarted.

Paul Lee schrieb:

Dear all,

I am currently having 4 LDAP servers running in 4-way masters mode, the current version is 2.4.9 and there are around 100k records.

The db version is 4.2.

If I want to upgrade to version 2.4.12, I should upgrade the db to 4.4 or above, right ?

but if the db version is upgraded, how to preserve my existing 100k records, any formal procedure to convert the data to the new format ?

Is my following procedure correct ?

• upgrade the db version to 4.4
• upgrade openldap in 1 machine to 2.4.12
• delete all the files in /usr/local/var/openldap-data
• stop 2 more openldap servers, leaving only 1 running version 2.4.9
• start the new server running version 2.4.12, then, records will be

created in 2.4.12.

• repeat for others servers.

Is this correct ?

Thanks

Confidential Communication - This e-mail (including any attachments) is confidential and may be legally privileged. If this e-mail has been sent to you by mistake please inform us by reply e-mail and then delete the e-mail, destroy any printed copy and do not disclose or use the information in it.

____________ Virus checked by G DATA AntiVirusKit Version: AVK 19.1177 from 23.10.2008 Virus news: www.antiviruslab.com

youre right, michael. as i mailed Rein Tollevik and Paul Lee a few minutes ago, thats absolutely correct: 2.4.12. needs 4.4+ http://www.openldap.org/software/release/readme.html my last 14 days were very busy, so it seems that i missed that release-info from 12/10/2008. thanks for pointing me there.

oliver

Michael Ströder schrieb:

Oliver Liebel wrote:

...

keep it simple. first, theres no need of upgrading your bdb.

Oliver, that's wrong! Please read the 2.4.12 Release README: "BDB and HDB backends require Oracle Berkeley DB 4.4, 4.5, 4.6, or 4.7."

...

if you want to upgrade your slapds und bdb, you should dump first your db files the traditional way (slapcat), there should be no need to "convert" your data when re-import them with slapadd.

That's right!

http://www.openldap.org/faq/data/cache/842.html http://www.openldap.org/faq/data/cache/288.html

Ciao, Michael.

____________ Virus checked by G DATA AntiVirusKit Version: AVK 19.1180 from 23.10.2008 Virus news: www.antiviruslab.com

yes, already corrected this yesterday: http://www.openldap.org/lists/openldap-technical/200810/msg00135.html

Paul Lee schrieb:

however, if I not upgrade to DB 4.4, I can't install openldap 2.4.12 because it failed in ./configure, it says that the BDB version failed.

checking for Berkeley DB major version in db.h... 4 checking for Berkeley DB minor version in db.h... 2 checking if Berkeley DB version supported by BDB/HDB backends... no configure: error: BerkeleyDB version incompatible with BDB/HDB backends

That's why I need to upgrade BDB version.

Oliver Liebel wrote:

...

keep it simple. first, theres no need of upgrading your bdb. 4.2.52 has the longest history to be stable. for bdb versions, see: http://www.openldap.org/lists/openldap-technical/200807/msg00138.html

if you want to upgrade your slapds und bdb, you should dump first your db files the traditional way (slapcat), there should be no need to "convert" your data when re-import them with slapadd. http://www.openldap.org/lists/openldap-software/200802/msg00289.html you should not use any bdb-internal upgrading-tools.

next: easiest way to upgrade surely will be to stop all slapds.

as mentioned above, before any upgrade, stop all slapds if possible (or at least one), then slapcat > dbdump.ldif on this master (e.g. master1). remove all old db-files except DB_CONFIG on all masters (if they are down) upgrade to 2.4.12 and the bdb you want (except 4.3) on all masters (if they are down) slapadd the ldif on master1, start this one first , then your other masters, they will fetch your dit from the first master, if your replication-config is setup correctly.

if you have to keep the system up (or just have a small downtime) then stop master1, slapcat, upgrade slapd and bdb, slapadd. stop the other masters, and then start master1. on the other masters just upgrade slapd and bdb and remove the old db-files, they should be synced from master1 when theyre slapds are restarted.

Paul Lee schrieb:

...

Dear all,

I am currently having 4 LDAP servers running in 4-way masters mode, the current version is 2.4.9 and there are around 100k records.

The db version is 4.2.

If I want to upgrade to version 2.4.12, I should upgrade the db to 4.4 or above, right ?

but if the db version is upgraded, how to preserve my existing 100k records, any formal procedure to convert the data to the new format ?

Is my following procedure correct ?

• upgrade the db version to 4.4
• upgrade openldap in 1 machine to 2.4.12
• delete all the files in /usr/local/var/openldap-data
• stop 2 more openldap servers, leaving only 1 running version 2.4.9
• start the new server running version 2.4.12, then, records will be

created in 2.4.12.

• repeat for others servers.

Is this correct ?

Thanks

Confidential Communication - This e-mail (including any attachments) is confidential and may be legally privileged. If this e-mail has been sent to you by mistake please inform us by reply e-mail and then delete the e-mail, destroy any printed copy and do not disclose or use the information in it.

---

Virus checked by G DATA AntiVirusKit Version: AVK 19.1177 from 23.10.2008 Virus news: www.antiviruslab.com

Confidential Communication - This e-mail (including any attachments) is confidential and may be legally privileged. If this e-mail has been sent to you by mistake please inform us by reply e-mail and then delete the e-mail, destroy any printed copy and do not disclose or use the information in it.

____________ Virus checked by G DATA AntiVirusKit Version: AVK 19.1193 from 24.10.2008 Virus news: www.antiviruslab.com