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

This task entry requires three attributes:
• A unique name (cn)
• The file name of the LDIF file to import (nsFilename)
• The name of the database into which to import the file (nsInstance)
It is also possible to supply the DNs of suffixes to include or exclude from the import, analogous
to the -s and -x options, respectively, for the ldif2db and ldif2db.pl scripts.
The entry is simply added using ldamodify, as described in “Adding and modifying entries using
ldapmodify” (page 112). For example:
ldapmodify -a -D "cn=directory manager" -w secret -p 389 -h server.example.com
dn: cn=example import, cn=import, cn=tasks, cn=config
objectClass: top
objectClass: extensibleObject
cn: example import
nsFilename: /home/files/example.ldif
nsInstance: userRoot
nsIncludeSuffix: ou=People,dc=example,dc=com
nsExcludeSuffix: ou=Groups,dc=example,dc=com
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 Directory Server import tasks under the cn=tasks entries.
4.2 Exporting data
LDAP Data Interchange Format (LDIF) files are used to export database entries from the Directory
Server databases. LDIF is a standard format described in RFC 2849, The LDAP Data Interchange
Format (LDIF) - Technical Specification.
Exporting data can be useful for the following:
• Backing up the data in the database.
• Copying data to another Directory Server.
• Exporting data to another application.
• Repopulating databases after a change to the directory topology.
For example, if a directory contains one database, and its contents are split into two databases,
then the two new databases receive their data by exporting the contents of the old databases and
importing it into the two new databases, as illustrated in Figure 6 (page 155).
NOTE:
The export operations do not export the configuration information (cn=config), schema information
(cn=schema), or monitoring information (cn=monitor).
154 Populating Directory Databases