LDAP Replicas 4.5.x to 5.0.x

Revision as of 20:08, 4 February 2008 by Mlo (talk | contribs)

UPDATED Information for those running LDAP Replicas:

-We strongly suggest that if you ever did an upgrade from 4.5.10 (or prior) -> 5.0.1 (or prior) at any time and have LDAP replicas, please go & refresh the replicas.

-Updating to 5.0.2 will not fix the data issues in the replicas. The only solution is to reload the replicas if you went from 4.5.10 (or prior) -> 5.0.1 (or prior).

Still in the 4.5.x series?

-If you make use of LDAP replicas & are still on 4.5.10 (or prior) please update to 4.5.11 before switching to 5.0.2

-When they come out, if you have LDAP replicas when going 4.5.11 > 5.0.2 you should still follow the directions given at LDAP Replicas 4.5.x to 5.0.x - Zimbra :: Wiki on updating the replica schemas before upgrading the master LDAP.

-Should you forget to follow these instructions when upgrading from 4.5.11 -> 5.0.2, don't despair! No harm to your ldap data will occur, however some parts of ZCS will not function correctly until all of the replicas are also upgraded to 5.0.2


-From 4.5.11, you will still run into the zimbraAdminURL bug when you take your master to 5.0.2, until all replicas are also on 5.0.2. You can avoid this by doing the same upgrade procedure we had for going from 4.5.10 (or prior) > 5.0.1 (or prior), where you update zimbra.schema on the replicas prior to upgrading the master.

The big difference between 4.5.10 and 4.5.11 on a v5 upgrade, is that if you choose not to upgrade zimbra.schema prior to upgrading the master, your replica DB will remain consistent with 4.5.11, whereas with 4.5.10 certain changes would not be propagated and the replica databases would be inconsistent from then on.


ZCS 4.5.x: If upgrading to any ZCS 5.0.x please use the workaround below.

This procedure allows all the replica servers to properly preserve the changes made to the master during the upgrade process and allows ZCS 5.0.x non-LDAP servers to work with the 4.5.x replica servers.

Choosing to remove your LDAP replicas during the upgrade and install fresh ones is also an alternative if you wish.

Schema workaround for ANY 4.5.x > 5.0.x migration:

If you have LDAP replica servers configured for ZCS, when you upgrade from 4.5.x to 5.0, you must modify each LDAP replica server before you upgrade the LDAP master server.

1. On each LDAP replica server perform the following:

Stop LDAP, as the zimbra user, type ldap stop
Change directors, type cd /opt/zimbra/openldap/etc/openldap/schema/
As the root user, type mv zimbra/schema zimbra.schema.old
As the root user, type wget http://files.zimbra.com/downloads/5.0.2_GA/zimbra.schema
As the root user, type chown zimbra:zimbra zimbra.schema
As the root user, type chmod 664 zimbra.schema
Restart the server, as the zimbra user, type ldap start

wget isn't available on macs. Use curl -O instead

2. Upgrade the LDAP master as described in the release notes

3. Upgrade the LDAP replicas

Fix for those who have already upgraded from 4.5.x to 5.0.1, and the replicas become out-of-sync:

On the Master:

  su - zimbra
 /opt/zimbra/openldap/sbin/slapcat -b '' -f /opt/zimbra/conf/slapd.conf -l /tmp/ldap.ldif
 scp /tmp/ldap.ldif root@replica:/tmp/ldif

On the Replica:

 chown zimbra:zimbra /tmp/ldap.ldif
 su - zimbra
 ldap stop
 mv /opt/zimbra/openldap-data /opt/zimbra/openldap-data-old
 mkdir -p /opt/zimbra/openldap-data/logs
 cp /opt/zimbra/openldap-data-old/DB_CONFIG /opt/zimbra/openldap-data
 chown -R zimbra:zimbra /opt/zimbra/openldap-data/
 su - zimbra
 /opt/zimbra/openldap/sbin/slapadd -w -q -b '' -f /opt/zimbra/conf/slapd.conf -l /tmp/ldap.ldif
 ldap start
Jump to: navigation, search