Replication Overview282 Netscape Directory Server Administrator’s Guide • August 2002The replication mechanism also requires that one database correspond to onesuffix. This means that you cannot replicate a suffix (or namespace) that isdistributed over two or more databases using custom distribution logic. For moreinformation on this topic, refer to “Creating and Maintaining Databases,” on page89.Replication IdentityWhen replication occurs between two servers, the replication process uses a specialentry, often referred to as the Replication Manager entry, to identify replicationprotocol exchanges. The Replication Manager entry, or any entry you create tofulfill that role, must meet the following criteria:• It is created on the consumer server (or hub supplier) and not on the supplierserver.• You must create this entry on every server that receives updates from anotherserver, that is on every hub supplier or a dedicated consumer.• When you configure a replica that receives updates from another server, youmust specify this entry as the one authorized to perform replication updates.• When you configure the replication agreement on the supplier server, youmust specify the DN of this entry in the replication agreement.• This entry must not be part of the replicated database for security reasons.• This entry, with its special user profile, bypasses all access control rulesdefined on the consumer server.For more information on creating the Replication Manager entry, refer to “Creatingthe Supplier Bind DN Entry,” on page 290.NOTE In the Directory Server Console, this Replication Manager entry isreferred to as the supplier bind DN, which may be misleading as theentry does not actually exist on the supplier server. It is called thesupplier bind DN because it is the entry which must be present onthe consumer for the supplier to be able to bind to the consumer.
