Red Hat Directory Server 8.0 Administrator's Guide

For information on setting up cascading replication, see Section 6, “Configuring Cascading
Replication”.
NOTE
Multi-master and cascading replication can be combined. For example, in the
multi-master scenario illustrated in Figure 8.2, “Multi-Master Replication (Two
Masters)”, server C and server D could be hub servers that would replicate to
any number of consumer servers.
3. Creating the Supplier Bind DN Entry
A critical part of setting up replication is to create the entry, called the replication manager or
supplier bind DN entry, that the suppliers use to bind to the consumer servers to perform
replication updates.
The supplier bind DN must meet the following criteria:
• It must be unique.
• It must be created on the consumer server (or hub) and not on the supplier server.
• It must correspond to an actual entry on the consumer server.
• It must be created on every server that receives updates from another server.
• It must not be part of the replicated database for security reasons.
• It must be defined in the replication agreement on the supplier server.
For example, the entry cn=Replication Manager,cn=config can be created under the
cn=config tree on the consumer server. This would be the supplier bind DN that all supplier
servers would use to bind to the consumer to perform replication operations.
NOTE
Avoid creating simple entries under the cn=config entry in the dse.ldif file.
The cn=cn=config entry in the simple, flat dse.ldif configuration file is not
stored in the same highly scalable database as regular entries. As a result, if
many entries, and particularly entries that are likely to be updated frequently, are
stored under cn=config, performance will suffer. However, although Red Hat
recommends not storing simple user entries under cn=config for performance
reasons, it can be useful to store special user entries such as the Directory
Creating the Supplier Bind DN Entry
275