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

nsArchiveDir: /home/backups/
nsDatabaseType: ldbm database
As soon as the task is completed, the entry is removed from the directory configuration.
The HP-UX Directory Server configuration, command, and file reference has more information on
the available attributes for running database restore tasks under the cn=tasks entries.
4.3.4 Restoring a single database
It is possible to restore a single database through the command line, but not in the Directory Server
Console. To restore a single database:
1. Stop the Directory Server if it is running.
/opt/dirsrv/slapd-instance_name/stop-slapd
For more information about the command to start and stop the HP-UX Directory Server,
see“Starting and Stopping Servers” (page 19).
2. Restore the back-end from the /var/opt/dirsrv/slapd-instance_name/bak archives
with the bak2db script, using the -n option to specify the database name. For example:
/opt/dirsrv/slapd-instance_name/bak2db \
/var/opt/dirsrv/slapd-instance_name/bak/backup_file -n userRoot
3. Start the Directory Server.
/opt/dirsrv/slapd-instance_name/start-slapd
NOTE:
If the Directory Server fails to start, remove the database transaction log files in
/var/opt/dirsrv/slapd-instance_name/db/log.###, then retry starting the server.
4.3.5 Restoring databases that include replicated entries
If a database that supplies entries to other servers is restored, then you must reinitialize all the
servers that receive updates from the restored database (for example, consumer servers, hub servers,
and, in multi-master replication environments, other supplier servers). The changelog associated
with the restored database will be erased during the restore operation. A message will be logged
to the supplier servers' log files indicating that reinitialization is required. If a database containing
data received from a supplier server is restored, then one of two situations can occur:
• Changelog entries have not yet expired on the supplier server.
If the supplier's changelog has not expired since the database backup was taken, then restore
the local consumer and continue with normal operations. This situation occurs only if the
backup was taken within a period of time that is shorter than the value set for the maximum
changelog age attribute, nsslapd-changelogmaxage, in the
cn=changelog5,cn=config entry. For more information about this option, see the HP-UX
Directory Server configuration, command, and file reference.
Directory Server automatically detects the compatibility between the replica and its changelog.
If a mismatch is detected, the server removes the old changelog file and creates a new, empty
one.
• Changelog entries have expired on the supplier server since the time of the local backup.
If changelog entries have expired, reinitialize the consumer. For more information on
reinitializing consumers, see “Initializing consumers” (page 371).
For information on managing replication, see “Managing Replication” (page 317).
164 Populating Directory Databases