You can create multiple local database backends, each containing one or more different base DNs. There should be at most one replicating domain on each local database backend. The replication domain should not span multiple local database backends. The typical entry-balancing configuration involves two local database backends: one backend to serve the global domain data that resides above the entry-balancing point and a backend that is defined with the entry-balancing point as the base DN, such as ou=people,dc=example,dc=com.

With multiple local database backends configured, the data existing with each backend can be managed independently. In addition, separate index settings are applied to each local database backend.

When creating multiple databse backends, consider the following:

  • No two backends may have the same base DN.
  • If any base DN for a given backend is subordinate to a base DN on another backend, then all base DNs on that backend must be subordinate to the base DN of the other backend.
  • The total of all db-cache-percent values should be no more than 65-70% in most cases and should never be configured to exceed 100%.