HP-UX Directory Server 8.1 administrator guide

changetype: modify
replace: nsds5beginreplicarefresh
nsds5beginreplicarefresh: start
ldapmodify does not prompt for input; simply type in the LDIF statement, then click Enter
twice when the LDIF statement is complete. Close the ldapmodify utility by entering
Ctrl-C.
When the initialization is complete, the nsds5beginreplicarefresh attribute is automatically
deleted from the replication agreement entry.
NOTE:
Initializing consumers from the command line is also explained in “Initializing consumers online
using the command line”. Manually initializing consumers is explained in “Manual consumer
initialization using the command line”. The replication monitoring attributes are described in
more detail in the HP-UX Directory Server configuration, command, and file reference.
To keep data integrity, initialize the consumer databases from the appropriate supplier. 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 the other master servers in the configuration from
one master.
• For cascading replication, initialize all the hubs from a supplier, then initialize the consumers
from the hubs.
8.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.
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”
• “Moving the changelog to a new location”
8.9.1 Removing the changelog
To remove the changelog from the supplier server:
372 Managing replication