Initializing The Replicas For Cascading Replication; Making A Replica Updatable; Deleting The Changelog - Red Hat DIRECTORY SERVER 7.1 - ADMINISTRATOR Administrator's Manual

Initializing the Replicas for Cascading Replication

In the case of cascading replication, you should initialize replicas in the following
order:
Use the supplier server to initialize the replica on the hub supplier.
1.
From the hub supplier, initialize the replica on the consumer.
2.
For information on initializing replicas, refer to "Initializing Consumers," on page
345.

Making a Replica Updatable

To make a read-only server writable, follow this procedure:
Make sure there are no updates in progress.
1.
Stop the supplier server.
2.
Open the Directory Server Console for the read-only replica.
3.
In the configuration tab, select Replication, and then, on the right pane, enable
4.
changelog.
Select the suffix, and, in the Replica Settings tab, change Replica Role to Single
5.
Master, and assign a unique replica ID.
Save your changes, and restart the server.
6.

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). In the event of a supplier server going 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. Once you have deleted the changelog, you can initialize your
consumers and begin the replication process afresh. To delete the changelog, you
can either remove it or move it to a new location.
This section contains the information for the following procedures:
• Removing the Changelog
Making a Replica Updatable
Chapter 8 Managing Replication 343