You can create multiple local database backends, each containing one or more different base distinguished names (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 serves the global domain data that resides above the entry-balancing point.
- One backend is defined with the entry-balancing point as the base DN, such as
With multiple local database backends configured, you can manage the data existing with each backend independently. Separate index settings are applied to each local database backend.
When creating multiple database backends, consider the following:
- No two backends can 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 exceed 100%.