Red Hat 8.1 Configuration And Command Reference page 87

the parameters of the task and initiates the task. As soon as the task is complete, the task entry is
removed from the directory.
T he cn=backup entry is a container entry for backup task operations. T he 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 nsArchiveDir
nsDatabaseT ypes 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 listed
in Section 2.3.15.1, "T ask Invocation Attributes for Entries under
nsArchiveDir
T his attribute gives the location of the directory to which to write the backup.
T he 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).
Parameter
Entry DN
Valid Values
Default Value
Syntax
Example
nsDatabaseT ypes
T his attribute gives the kind of database being archived. Setting the database types signals what kind of
backup plug-in the Directory Server should use to archive the database.
Parameter
Entry DN
Valid Values
Default Value
Syntax
Example
2.3.15.5. cn=restore
A database can be restored 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.
T he cn=restore entry is a container entry for task operations to restore a database. T he
cn=restore entry itself has no attributes, but each of the task entries within this entry, such as
cn=task_ID, cn=restore, cn=tasks, cn=config, uses the following attributes to define the restore
task.
A restore task entry under cn=restore must contain the location of the directory from which to retrieve
the archive copy (in the nsArchiveDir
nsDatabaseT ypes attribute). Additionally, it must contain a unique cn to identify the task. For example:
dn: cn=example restore, cn=restore, cn=tasks, cn=config
objectclass: extensibleObject
cn: example restore
nsArchiveDir: /export/backups/
nsDatabaseType: ldbm database
As the restore operation runs, the task entry will contain all of the server-generated task attributes listed
in Section 2.3.15.1, "T ask Invocation Attributes for Entries under
Red Hat D irectory Server 8.1 Configuration and Command Reference
attribute) and the type of database being backed up (in the
Description
cn=task_name, cn=backup, cn=tasks, cn=config
Any local directory location
Case-exact string
nsArchiveDir: /export/backups
Description
cn=task_name, cn=backup, cn=tasks, cn=config
ldbm database
ldbm database
Case-exact string
nsDatabaseT ype: ldbm database
attribute) and the type of database being restored (in the
cn=tasks".
cn=tasks".
87