Binary Restore

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.

To Restore Your Server

You can use DSCC to perform this task. For information, see Directory Service Control Center Interface and the DSCC online help.

1. 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/ds/ local/ds/bak/2006_07_01_11_34_00

   • If your server is remote and 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/ds/bak/2006_07_01_11_34_00

   For more information about these commands, see the dsadm(1M) and dsconf(1M) man pages.

Restoring the dse.ldif Configuration File

Directory Server creates two backup copies of the dse.ldif file in the following directory:

instance-path/config

The dse.ldif.startOK file records a copy of the dse.ldif file at server start up. The dse.ldif.bak file contains a backup of the most recent changes to the dse.ldif file. Copy the file that contains the most recent changes to your directory.

To Restore the dse.ldif Configuration File

For parts of this procedure, you can use DSCC to perform this task. For information, see Directory Service Control Center Interface and the DSCC online help. Other parts of the procedure can only be done using the command line.

1. Stop the server.

   $ dsadm stop instance-path

2. Change to the directory that contains the configuration files.

   $ cd instance-path/config

3. Overwrite the dse.ldif file with a backup configuration file that is known to be valid, for example:

   $ cp dse.ldif.startOK dse.ldif

4. Start the server with the following command:

   $ dsadm start instance-path