The following procedures describe how to restore suffixes in your directory. Your server must have been backed up using the procedures described in Backing Up Directory Data Only. Before restoring suffixes involved in replication agreements, read Restoring Replicated Suffixes.
Do not stop the server during a restore operation. Because restoring your server overwrites any existing database files, any modifications that were made to the data since the backup are lost.
You can use DSCC to perform this task. For information, see Directory Service Control Center Interface and the DSCC online help.
Use one of the following commands to restore your server:
If your server is local and stopped, type:
$ dsadm restore instance-path archive-dir
For example, to restore a backup from a backup directory, type:
$ dsadm restore /local/dsInst/ local/ds/bak/2006_07_01_11_34_00
If your server is running, type:
$ dsconf restore -h host -p port archive-dir
For example, to restore a backup from a backup directory:
$ dsconf restore -h host1 -p 1389 /local/dsInst/bak/2006_07_01_11_34_00
Do not stop the server during a restore operation.
The backup copy must be saved on the server, not on the system that is running the dsconf command.
After a restore, there is no way to go back to the original server content.
To save disk space, you can restore server by moving files in place of copying them. You can perform this operation by setting the —f move-archive flag with the dsadm restore or the dsconf restore command. However, if the transaction logs cannot be moved during the copyless restore operation, the copy operation is performed instead.
For this operation to complete successfully, the backup and instance files must be on the same filesystem. If you choose to perform the copyless restore, the server data is overwritten with the data in the backup copy and the backup copy also gets destroyed.