Performing disaster recovery
If data is compromised across all systems and a restore is necessary, you can perform disaster recovery.
About this task
Consider the following for disaster recovery:
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, such as if an errant application mistakenly wipes out some data. |
For more information about LDIF exports, see LDIF export as a recurring task.
These steps assume that no server performs read or write operations during this process. |
To complete a restore of your systems and perform a disaster recovery:
Steps
-
Stop all servers.
-
Go to one of the servers and remove it from the topology:
Example:
bin/remove-defunct-server --performLocalCleanup --no-prompt
-
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 thebin/import-ldif
command. -
Start the restored server. The server can now receive client requests.
-
Clean up replication artifacts from the next server before starting it up:
Example:
bin/remove-defunct-server --performLocalCleanup --no-prompt
-
Start the server in lockdown mode with the following command:
Example:
bin/start-server --skipPrime --lockdownMode
-
Enable replication from the first server to the second server.
Example:
bin/dsreplication enable
-
Initialize the second server from the first with the following command:
Example:
bin/dsreplication initialize
-
Restart the second server or use the
bin/leave-lockdown-mode
command to exit lockdown mode.The second server can now receive client requests.
-
Repeat steps 5 through 10 for any other servers.