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.
DB_CONFIG.custom
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. To set up a customized DB_CONFIG, copy this file to DB_CONFIG.custom in the same directory. Then make whatever modifications necessary for the local installation to this file. To put your DB_CONFIG.custom file into place, stop ldap by running "ldap stop" as the zimbra user, and then rm /opt/zimbra/openldap-data/DB_CONFIG. Now run "ldap start" as the zimbra user. Your new customized DB_CONFIG will be installed. This is the procedure to follow any time modifications are made to /opt/zimbra/openldap/var/openldap-data/DB_CONFIG.custom.
DB_CONFIG.accesslog.custom
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. To set up a customized DB_CONFIG file for the accesslog database, cd /opt/zimbra/openldap/var/openldap-data on the master LDAP server. Copy DB_CONFIG.accesslog to DB_CONFIG.accesslog.custom, and then make whatever modifications are necessary for the local installation to this file. On the master, run "ldap stop" as the zimbra user, then rm /opt/zimbra/openldap-data/accesslog/db/DB_CONFIG. Now run "ldap start" as the zimbra user. The new customized DB_CONFIG file for the accesslog database will now be in place.
