Backing Up And Restoring Data - Red Hat DIRECTORY SERVER 8.0 - ADMINISTRATION Administration Manual

Chapter 4. Populating Directory Databases
The LDIF file in this case would be /var/lib/dirsrv/slapd-instance_name/
ldif/instance_name-example-2007_04_30_112718.ldif, using the name of the suffix
rather than the database.
If the suffix specified is a root suffix, such as dc=example,dc=com, then it is not necessary to
specify the database or to use the -n option.
For more information about using this script, see the Directory Server Configuration, Command,
and File Reference.
Option
-n
-s
-a
-r
-E
Table 4.4. db2ldif Options

4.3. Backing up and Restoring Data

Databases can be backed up and restored using the Directory Server Console or a command-line
script.
Section 4.3.1, "Backing up All Databases"
•
Section 4.3.2, "Backing up the dse.ldif Configuration File"
•
Section 4.3.3, "Restoring All Databases"
•
Section 4.3.4, "Restoring a Single Database"
•
Section 4.3.5, "Restoring Databases That Include Replicated Entries"
•
Section 4.3.6, "Restoring the dse.ldif Configuration File"
•
104
Description
Specifies the name of the database from which
the file is being exported.
Specifies the suffix or suffixes to include in
the export. If the suffix is a root suffix, such as
dc=example,dc=com, then the -n option is not
required. There can be multiple -s arguments.
Defines the output file to which Directory
Server exports the LDIF. This file must be an
absolute path. If the -a option is not given,
the output ldif is stored in the the /var/lib/
dirsrv/slapd-instance_name/ldif
directory and is automatically named serverID-
database-YYYY_MM_DD_hhmmxx.ldif
with the -n option or serverID-firstsuffixvalue-
YYYY_MM_DD_hhmmxx.ldif with the -s
option.
Specifies that the exported database is a
consumer replica. In this case, the appropriate
settings and entries are included with the LDIF to
initialize the replica when the LDIF is imported.
Decrypts an encrypted database so it can be
exported.