Skip Navigation Links | |
Exit Print View | |
Oracle Directory Server Enterprise Edition Administration Guide 11g Release 1 (11.1.1.5.0) |
Part I Directory Server Administration
2. Directory Server Instances and Suffixes
3. Directory Server Configuration
6. Directory Server Access Control
7. Directory Server Password Policy
8. Directory Server Backup and Restore
Backing Up Directory Data Only
To Back Up Your Directory Data
Restoring the Supplier in a Single-Master Scenario
Restoring a Supplier in a Multi-Master Scenario
Restoring a Dedicated Consumer
Restoring a Master in a Multi-Master Scenario
To Begin Accepting Updates Through the Command Line
To Make a Backup for Disaster Recovery
To Restore for Disaster Recovery
9. Directory Server Groups, Roles, and CoS
10. Directory Server Replication
13. Directory Server Attribute Value Uniqueness
15. Directory Server Monitoring
Part II Directory Proxy Server Administration
16. Directory Proxy Server Tools
17. Directory Proxy Server Instances
19. Directory Proxy Server Certificates
20. Directory Proxy Server Load Balancing and Client Affinity
21. Directory Proxy Server Distribution
22. Directory Proxy Server Virtualization
23. Virtual Data Transformations
24. Connections Between Directory Proxy Server and Back-End LDAP Servers
25. Connections Between Clients and Directory Proxy Server
26. Directory Proxy Server Client Authentication
27. Directory Proxy Server Logging
28. Directory Proxy Server Monitoring and Alerts
Part III Directory Service Control Center Administration
Backing up to LDIF allows you to back up directory data to a formatted LDIF file.
You can back up directory data by exporting the contents of a suffix in the LDIF format. Exporting data can be useful for doing the following:
Backing up the data in your server
Copying your data to another directory server
Exporting your data to another application
Repopulating suffixes after a change to your directory topology
The configuration information cannot be exported.
Suffix data can occupy a large amount of disk space, especially files in LDIF format. You can optimize transfer times and disk space by exporting compressed files. When you export suffix data, if the filename of the export file ends with .gz, ODSEE automatically compresses the file. By default the compression level is 3. If you increase the compression level, the CPU usage grows significantly while the files size do not show a comparatively significant shrink.
The level range is a number between 1 and 9. Other values revert to default level 3. Compression level is ignored if the output LDIF does not end with .gz.
Caution - Do not stop the server while an export operation is in progress. |
You can use DSCC to perform this task. For information, see Directory Service Control Center Interface and the DSCC online help.
If your server is local and stopped, type:
$ dsadm export instance-path suffix-DN LDIF-file
The dsadm export takes only offline backups.
If your server is running (local or remote), type:
$ dsconf export -h host -p port suffix-DN LDIF-file
The dsconf export takes only online backups.
The following example uses dsconf export to export two suffixes to a single LDIF file:
$ dsconf export -h host1 -p 1389 ou=people,dc=example,dc=com \ ou=contractors,dc=example,dc=com /local/dsInst/ldif/export123.ldif
The ldif file will be created on the machine running the server instance not on the machine running the dsconf command.
The dsadm export and dsconf export commands can also be used with the --no-repl option to specify that no replication information is to be exported. The default is that the replicated suffix is exported to an LDIF file with replication information. The resulting LDIF file will contain attribute subtypes that are used by the replication mechanism. This LDIF file can then be imported on the consumer server to initialize the consumer replica, as described in Initializing Replicas
For more information about these commands, see the dsadm(1M) and dsconf(1M) man pages.