You can only restore a single backend at a time, and that backend will be offline for the duration of the restore process. The directory containing the backup used for the restoration includes a backup.info file with information about the backup, including when the backup was generated and whether the backup is compressed, signed, or encrypted.

You can use the restore command for the following data recovery scenarios:

  • To restore a single backend in a replicated topology, run the dsreplication initialize command.

    This command streams the contents of the backend database from the source to the destination and ensures that the server receives the most up-to-date version of the data.

  • To restore a backup in a non-replicated instance, run the restore command and specify the path to the directory containing the backup. 
    $ bin/restore --backupDirectory /path/to/backup
  • To restore a backup to a point-in-time:
    1. Run dsreplication pre-external-initialization on a server in the topology.
    2. Choose the required baseDN.
    3. Stop the server.
    4. Restore that server to your desired point-in-time backup.
    5. Re-start the server.
    6. Run dsreplication initialize-all.
    7. Initialize all other servers in the topology from the restored server.
    8. Run dsreplication post-external-initialization on the restored server.
  • If all of your servers have been compromised:
    1. Build a directory server.
    2. Restore from the latest backup.
    3. If available, use the extract-data-recovery-log-changes command to replay changes in the data recovery log.

      For more information, see Reverting or replaying changes.

    4. Add and initialize new directory servers from the one that you just restored.