Red Hat DIRECTORY SERVER 8.1 Command Reference Manual page 127

Parameter
Entry DN
Valid Values
Default Value
Syntax
Example
nsDumpUniqId
This attribute sets that the unique IDs for the exported entries are not exported.
Parameter
Entry DN
Valid Values
Default Value
Syntax
Example
2.3.15.4. cn=backup
A database can be backed up through the command line by creating a special task entry which
defines the parameters of the task and initiates the task. As soon as the task is complete, the task
entry is removed from the directory.
The cn=backup entry is a container entry for backup task operations. The cn=backup entry itself
has no attributes, but each of the task entries within this entry, such as cn=task_ID, cn=backup,
cn=tasks, cn=config, uses the following attributes to define the backup task.
A backup task entry under cn=backup must contain the location of the directory to which to copy
the archive copy (in the
nsDatabaseTypes
attribute). Additionally, it must contain a unique cn to identify the task. For example:
dn: cn=example backup, cn=backup, cn=tasks, cn=config
objectclass: extensibleObject
cn: example backup
nsArchiveDir: /export/backups/
nsDatabaseType: ldbm database
As the backup operation runs, the task entry will contain all of the server-generated task attributes
Section 2.3.15.1, "Task Invocation Attributes for Entries under
listed in
nsArchiveDir
This attribute gives the location of the directory to which to write the backup.
The backup directory here should usually be the same as the one configured in the nsslapd-bakdir
attribute.
If this attribute is not included with the cn=backup task, the task will fail with an LDAP object class
violation error (65).
nsArchiveDir
attribute) and the type of database being backed up (in the
Description
cn=task_name, cn=export, cn=tasks, cn=config
true | false
false
Case-insensitive string
nsNoWrap: false
Description
cn=task_name, cn=export, cn=tasks, cn=config
true | false
false
Case-insensitive string
nsDumpUniqId: true
cn=tasks".
cn=tasks
113