Red Hat Directory Server 8.0 Administrator's Guide

8. Stop the destination Directory Server if it is running.
service dirsrv stop slapd-example2
9. On the destination server, restore the archives with the bak2db script, using the optional -n
parameter to specify the backend instance name. This -n parameter is similar to the -n used
with ldif2db and db2ldif. For example:
/usrlib/dirsrv/slapd-example2/bak2db /tmp/archiveDirectory -n userRoot
10.Restart the destination Directory Server. For example:
service dirsrv start slapd-example2
Replication will begin on schedule as soon as the destination server is restarted.
For more information on using these scripts, see the Directory Server Configuration, Command,
and File Reference.
11. Forcing Replication Updates
When a Directory Server involved in replication is stopped for regular maintenance, it must be
updated immediately when it comes back online. In the case of a supplier in a multi-master
environment, the directory information needs to be updated by the other supplier in the
multi-master set. In other cases, when a hub or a dedicated consumer is taken offline for
maintenance, when they come back online, they need to be updated by the supplier server.
Even if the replication agreements are configured to keep the supplier and consumer servers
always in sync, it is not sufficient to bring back up-to-date a server that has been offline for over
five minutes. The Always Keep in Sync option means that the server generates a replication
operation for every update operation it processes. However, if this replication operation cannot
be performed because the consumer is offline, the operation times out after 10 minutes.
NOTE
The procedures described in this section can only be used when replication is
already set up and consumers have been initialized.
To ensure that directory information will be synchronized immediately when a server comes
back online, use either the Directory Server Console on the supplier server that holds the
reference copy of the directory information or a customizable script.
Forcing Replication Updates
329