Red Hat Directory Server 8.0 Administrator's Guide

nsds5ReplicaPurgeDelay: 604800
nsds5ReplicaBindDN: cn=replication manager,cn=config
nsds5flags: 1
This entry identifies the database and suffix as participating in replication and sets what kind
of replica the database is. There are five key attributes:
• nsds5replicaroot sets the subtree (suffix) which is being replicated.
• nsds5replicatype sets what kind of replica this database is. For a hub, this value must be 2.
• nsds5ReplicaPurgeDelay sets how long the hub holds onto its change record before
deleting it. The default value is 604800 (one week).
• nsds5ReplicaBindDN give the DN as which the supplier will bind to the hub to make
changes.
• nsds5flags sets whether the replica writes to the changelog. For a hub, this value must be
1.
The replica entry attributes are described in Table 8.2, “Replica Attributes”. These attributes are
described in more detail in the Directory Server Configuration, Command, and File Reference.
7.4. Configuring Replication Agreements from the Command
Line
When setting up replication agreements, first set them up between all suppliers, then between
the suppliers and the hubs, and last between the hub and the consumers.
The replication agreement has to define seven things:
• The consumer host (nsds5replicahost) and port (nsds5replicaport).
• The DN for the supplier to use to bind with the consumer (nsds5ReplicaBindDN), the way
that the supplier binds (nsds5replicabindmethod), and any credentials required
(nsds5replicabindcredentials).
• The subtree being replicated (nsds5replicaroot).
• The replication schedule (nsds5replicaupdateschedule).
• Any attributes which will not be replicated (nsds5replicatedattributelist).
Use ldapmodify to add a replication agreement to every supplier for every consumer which it
will updated. For example:
dn: cn=ExampleAgreement,cn=replica,cn="dc=example,dc=com",cn=mapping
Line
317