HP-UX Directory Server 8.1 administrator guide
In addition, a new backup can be created by clicking the Back Up Directory Server button
in the Tasks tab of the Directory Server Console, then putting the name of the archive
directory in the Directory:... field. Alternatively, select any previous backup to initialize the
consumer.
This backup information is recovered in the destination replica.
6. Restart the source Directory Server. For example:
/opt/dirsrv/slapd-instance_name/restart-slapd
7. Copy the archived files to a directory on the destination server, such as archiveDirectory.
8. Stop the destination Directory Server if it is running.
/opt/dirsrv/slapd-instance_name/stop-slapd
9. On the destination server, restore the archives with the bak2db script, using the optional
-n option to specify the back-end instance name. This -n option is similar to the -n used
with ldif2db and db2ldif. For example:
/opt/dirsrv/slapd-example2/bak2db /tmp/archiveDirectory -n userRoot
10. Start the destination Directory Server. For example:
/opt/dirsrv/slapd-instance_name/start-slapd
Replication will begin on schedule as soon as the destination server is restarted.
For more information on using these scripts, see the HP-UX Directory Server configuration, command,
and file reference.
8.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 synchronized, 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.
8.11.1 Forcing replication updates from the console
To ensure that replication updates are sent immediately when a consumer or a supplier in a
multi-master replication configuration comes back online after a period of time, do the following
on the supplier server that holds the most recent version of the directory information:
1. In the Directory Server Console, click the Configuration tab, expand the Replication folder
and database nodes, and select the replication agreement corresponding to the replica to
update.
2. Right click the replication agreement, and choose Send Updates Now from the drop-down
list.
8.11 Forcing replication updates 377