Page created: 4 Feb 2020 |
Page updated: 22 Jul 2020
Note: The following should be considered for disaster recovery:
- With the default configuration, the server automatically exports all data nightly using the Export All Non-Administrative Backends recurring task. Up to seven days of exports are maintained. It is recommended that these be archived on another system.
- The Data Recovery Log logs all changes in a reversible format to logs/data-recovery/data-recovery.
- The bin/extract-data-recovery-log-changes tool provides the ability to redo or undo any changes from the logs/data-recovery/data-recovery logs.
- The combination of these allows you to either rebuild the data set to any point in time or to revert specific changes on a live data set (for example, if an errant application mistakenly wipes out some data).
Note: See LDIF Export as a Recurring Task for information about LDIF exports.
- Stop all servers.
Run the following command on all servers:
$ /bin/dsreplication cleanup-local-server
- Locate the backup or exported LDIF file that represents the last working copy of the database.
- Restore the backup or import the LDIF file on a single server. If importing an LDIF file, use the --excludeReplication option with the import-ldif command.
- Start the restored server. The server can now receive client requests.
Start another server in lockdown mode with the following command:
$ start-server --skipPrime --lockdownMode
- Enable replication from the first server to the second server.
Initialize the second server from the first with the following command:
$ bin/dsreplication initialize
- Restart the second server or use the bin/leave-lockdown-mode command to leave the server in lockdown mode. The second server can now receive client requests.
- Repeat steps 6 through 9 for any other servers.