Configuring the Directory Server
Configuring Security in the Directory Server
Configuring Replication With dsreplication
To Enable Replication Between Two Servers
To Initialize a Replicated Server
To Initialize an Entire Topology
To Obtain the Status of a Replicated Topology
Modifying the Replication Configuration With dsconfig
Retrieving the Replication Domain Name
Changing the Replication Purge Delay
To Change the Replication Purge Delay
Changing the Heartbeat Interval
To Change the Heartbeat Interval
To Change the Isolation Policy
Configuring Encrypted Replication
To Configure Encrypted Replication
Configuring Replication Groups
To Configure A Replication Group
Configuring Assured Replication
To Configure Assured Replication in Safe Data Mode
To Configure Assured Replication in Safe Read Mode
Configuring Replication Status
To Configure the Degraded Status Threshold
Initializing a Replicated Server With Data
Initializing a Single Replicated Server
Initializing a New Replicated Topology
Adding a Directory Server to an Existing Replicated Topology
Configuring Schema Replication
Replicating to a Read-Only Server
To Configure a Replica as Read-Only
Detecting and Resolving Replication Inconsistencies
Changing the data set implies importing an entirely new set of data to every directory server in the topology. When the data set is changed, two tasks are performed:
The new data is applied to each directory server in the topology.
The replication servers are cleared of any changes they might contain. This task includes resetting the data generation on the directory servers so that the new data generation is used.
If you change the data set using the dsreplication initialize command, both of these tasks are performed automatically. However, if you use the import-ldif command or the binary copy method to change the data set, you must perform these tasks manually, as described in the following section.
It is sufficient to run this command on only one directory server in the topology. All directory servers in the topology will be updated, unless you specify that only one server should be updated. For example, the following command prepares all servers in the topology for initialization by using import-ldif or binary copy:
$ dsreplication pre-external-initialization -h host1 -p 4444 -X \ -b dc=example,dc=com -I admin -w password Are you going to initialize only the contents of server host1:4444 (type 'no' if you will initialize contents of all replicated servers for the given Base DNs)? (yes / no) [no]: Preparing base DN dc=example,dc=com to be initialized externally ..... Done. Now you can proceed to the initialization of the contents of the base DNs on all the replicated servers. You can use the command import-ldif or the binary copy to do so. When the initialization is completed you must use the subcommand {post-external-initialization} for replication to work with the new base DNs contents.
It is sufficient to run this command on only one directory server in the topology. All other directory servers are updated. For example, the following command resets the generation ID for all directory servers in the topology after initialization using import-ldif or binary copy:
$ dsreplication post-external-initialization -h localhost \ -p 4444 -b dc=example,dc=com -I admin -w password -X Updating replication information on base DN dc=example,dc=com ..... Done. Post initialization procedure completed successfully.