HP-UX Directory Server Administrator Guide HP-UX Directory Server Version 8.1 (5900-3098, May 2013)

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.
8.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.
• “Removing the changelog” (page 371)
• “Moving the changelog to a new location” (page 371)
8.9.1 Removing the changelog
To remove the changelog from the supplier server:
1. In the Directory Server Console, select the Configuration tab.
2. Select the Replication Agreements folder in the left navigation tree, then select the Supplier
Server Settings tab in the right pane.
3. Clear the Enable Changelog checkbox.
This deletes the changelog.
4. Click Save.
5. Restart the Directory Server.
6. Reinitialize the consumers, as in “Initializing consumers” (page 371).
NOTE:
If the changelog is removed, the consumer servers must be reinitialized.
8.9.2 Moving the changelog to a new location
To delete the changelog while the server is still running and continuing to log changes, move the
changelog to a new location. By moving the changelog, a new changelog is created in the specified
directory, and the old changelog is deleted. Changing the location of the changelog requires
consumer reinitialization.
NOTE: In the previous releases, backup or restoring the main DB does not include changelog
DB. After restoring the main DB from the backup, running consumer initialization is a must to
regenerate the changelog.
Now, the back up utility db2bak[.pl] and the backup on console includes the changelog db in
the backed up database.
8.10 Initializing consumers
After a replication agreement is created, the consumer must be initialized; that is, the data must
be physically copied from the supplier server to the consumer servers. This section first describes
consumer initialization in detail, then provides instructions on the two different methods for initializing
consumers.
8.9 Deleting the changelog 371