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

This method of initializing consumers is especially useful in replication over wide-area networks
or over networks with slow or unstable connections.
For smaller databases, HP recommends using manual initialization or initialize consumers from
the Console.
NOTE:
The destination server must have the same architecture and the same bit size as the supplier server
for the initialization to succeed.
8.10.5.1 Initializing the consumer replica from the backup files
1. Create a new database on the destination server to match the database from the source server.
Before initializing the consumer from the backup files, be certain that the appropriate database
has been created on the destination server so that the database exists to be restored and
initialized.
2. Enable replication on the back-end as a dedicated consumer.
3. If there is already a replication agreement to that host and port, then replication should resume
immediately after running the restore script. Otherwise, create the replication agreement on
the source server (or whatever server is the supplier), and select the Do not initialize consumers
at this time radio button.
4. Stop the source Directory Server if it is running. For example:
/opt/dirsrv/slapd-instance_name/stop-slapd
5. From the command line, run the db2bak utility, and archive the current directory installation.
/opt/dirsrv/slapd-instance_name/db2bak
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.
8.11 Forcing replication updates 375