Managing Customized BDB configurations

 - This is certified documentation and is protected for editing by Zimbra Employees & Moderators only.

Successfully maintaining a customized BDB configuration file

As noted in the Performance Tuning Guidelines for Large Deployments article, it may be necessary to create and maintain a customized DB_CONFIG file for a given LDAP installation. Zimbra has created an easy to follow methodology allowing these customizations to be preserved across upgrades, and to be easily transferred to new LDAP servers at installation time.

Primary database custom DB_CONFIG file

After installation of the zimbra-ldap package, the directory /opt/zimbra/openldap/var/openldap-data will exist. Inside that directory will be the DB_CONFIG file used for the main database.

For ZCS 6.0.2 and later

As the zimbra user, do the following:

mkdir -p /opt/zimbra/conf/custom/ldap
cp /opt/zimbra/openldap/var/openldap-data/DB_CONFIG /opt/zimbra/conf/custom/ldap/DB_CONFIG

Make whatever modifications necessary for the local installation to this file. Then:

$ ldap stop
$ rm /opt/zimbra/data/ldap/hdb/db/DB_CONFIG
$ ldap start

Your new customized DB_CONFIG will be installed. If further modifications are made to the custom DB_CONFIG file, you will need to stop ldap, remove the existing DB_CONFIG file as above, and then restart ldap to have the new custom one copied into place.

For ZCS 6.0.1 and previous

As the zimbra user, do the following:

cp /opt/zimbra/openldap/var/openldap-data/DB_CONFIG /opt/zimbra/openldap/var/openldap-data/DB_CONFIG.custom

Make whatever modifications necessary for the local installation to this file. Then:

$ ldap stop

On 5.0.x installs:

$ rm /opt/zimbra/openldap-data/DB_CONFIG

On 6.0.0 and 6.0.1 installs:

$ rm /opt/zimbra/data/ldap/hdb/db/DB_CONFIG

Then

$ ldap start

Your new customized DB_CONFIG will be installed. If further modifications are made to the custom DB_CONFIG file, you will need to stop ldap, remove the existing DB_CONFIG file as above, and then restart ldap to have the new custom one copied into place.

Accesslog database custom DB_CONFIG file

It may also be necessary to make local modifications to the DB_CONFIG file used by the accesslog database on an LDAP master. This is almost identical to the method for maintaining a customized DB_CONFIG file for the main database.

For ZCS 6.0.2 and later

As the zimbra user, do the following on the ldap master:

cp opt/zimbra/openldap/var/openldap-data/DB_CONFIG.accesslog /opt/zimbra/conf/custom/ldap/DB_CONFIG.accesslog

Make whatever modifications necessary for the local installation to this file. Then:

$ ldap stop
$ rm /opt/zimbra/data/ldap/accesslog/db/DB_CONFIG
$ ldap start

The new customized DB_CONFIG file for the accesslog database will now be in place. If further modifications are made to the custom accesslog DB_CONFIG file, you will need to stop ldap, remove the existing DB_CONFIG file as above, and then restart ldap to have the new custom one copied into place.

For ZCS 6.0.1 and previous

As the zimbra user, do the following on the ldap master:

cd /opt/zimbra/openldap/var/openldap-data
cp DB_CONFIG.accesslog DB_CONFIG.accesslog.custom

Make whatever modifications necessary for the local installation to this file. Then:

$ ldap stop

On 5.0.x installs:

$ rm /opt/zimbra/openldap-data/accesslog/db/DB_CONFIG

On 6.0.0 and 6.0.1 installs:

$ rm /opt/zimbra/data/ldap/accesslog/db/DB_CONFIG

$ ldap start

The new customized DB_CONFIG file for the accesslog database will now be in place. If further modifications are made to the custom accesslog DB_CONFIG file, you will need to stop ldap, remove the existing DB_CONFIG file as above, and then restart ldap to have the new custom one copied into place.