Red Hat Directory Server 8.0 Administrator's Guide

Depending on the replication scenario, this can be more difficult in mixed replication
environments, but, even when manually initializing consumers, consider four things:
• Use one supplier, a data master, as the source for initializing consumers.
• Do not reinitialize a data master when the replication agreements are created. For example,
do not initialize server1 from server2 if server2 has already been initialized from server1.
• For a multi-master scenario, initialize all of the other master servers in the configuration from
one master.
• For cascading replication, initialize all of the hubs from a supplier, then initialize the
consumers from the hubs.
8. Making a Replica Updatable
Making a read-only server writable means changing the replica from a dedicated consumer or a
hub to a supplier.
1. Make sure there are no updates in progress.
2. Stop the supplier server.
3. Open the Directory Server Console for the read-only replica.
4. In the Configuration tab, select Replication. In the right pane, select the Enable changelog
checkbox.
5. Select the suffix, and, in the Replica Settings tab, change the replica role to a single master
or multi-master, and assign a unique replica ID.
6. Save the changes, and restart the server.
9. Deleting the Changelog
The changelog is a record of all modifications on a given replica that the supplier uses to replay
these modifications to replicas on consumer servers (or suppliers in the case of multi-master
replication). If a supplier server goes offline, it is important to be able to delete the changelog
because it no longer holds a true record of all modifications and, as a result, should not be used
as a basis for replication. After deleting the changelog, reinitialize the consumers and begin the
replication process afresh. To delete the changelog, either remove it or move it to a new
location.
• Section 9.1, “Removing the Changelog”
• Section 9.2, “Moving the Changelog to a New Location”
Chapter 8. Managing Replication
322