Red Hat DIRECTORY SERVER 7.1, Administrator'S Manual

Page: 165 / 652

Backing Up and Restoring Data
Chapter 4 Populating Directory Databases 165
• Changelog entries have not yet expired on the supplier server.
If the supplier server changelog has not expired since the database backup was
taken, then you can 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 you have set for the maximum changelog
age attribute. This attribute is called
nsslapd-changelogmaxage
and can be
found in the
cn=changelog5,cn=config
entry. For more information about
this option, refer to the
Red Hat 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, you need to initiate consumer
reinitialization. For more information on reinitializing consumers, refer to
“Initializing Consumers,” on page 345.
For information on managing replication, see “Managing Replication,” on
page 301.
Restoring the dse.ldif Configuration File
To restore the
dse.ldif
configuration file, stop the server, then use the procedure
outlined in “Restoring a Single Database,” on page 164, to copy the backup copy of
the
dse.ldif
file into your directory. Once you have copied the data, restart your
server.
The directory creates two backup copies of the
dse.ldif
file in this directory:
serverRoot
/slapd-
serverID
/config
The
dse.ldif.startOK
file records a copy of the
dse.ldif
file at server start up.
The
dse.ldif.bak
file contains a backup of the most recent changes to the
dse.ldif
file. Copy the file with the most recent changes to your directory.