Chapter 7. Managing data loss
Respond to data loss events by isolating affected servers or manually restoring lost information. You can determine the appropriate recovery method based on whether the data loss is isolated to specific replicas or has propagated across the entire environment.
7.1. Responding to isolated data loss Copy linkLink copied to clipboard!
If the data loss occurs, minimize the spread of corrupted data by immediately isolating the affected servers from the replication topology and replacing them with new replicas created from the remaining healthy servers.
Prerequisites
- A robust IdM replication topology with multiple replicas. See Preparing for server loss with replication.
Procedure
To limit replicating the data loss, disconnect all affected replicas from the rest of the topology by removing their replication topology segments.
Display all
domainreplication topology segments in the deployment.ipa topologysegment-find
[root@server ~]# ipa topologysegment-findCopy to Clipboard Copied! Toggle word wrap Toggle overflow Copy to Clipboard Copied! Toggle word wrap Toggle overflow Delete all
domaintopology segments involving the affected servers.ipa topologysegment-del
[root@server ~]# ipa topologysegment-delCopy to Clipboard Copied! Toggle word wrap Toggle overflow Suffix name: domain Segment name: segment1 ----------------------------- Deleted segment "segment1" -----------------------------
Suffix name: domain Segment name: segment1 ----------------------------- Deleted segment "segment1" -----------------------------Copy to Clipboard Copied! Toggle word wrap Toggle overflow Identify the
catopology segments that involve the restored server.ipa topologysegment-find
[root@server ~]# ipa topologysegment-findCopy to Clipboard Copied! Toggle word wrap Toggle overflow Copy to Clipboard Copied! Toggle word wrap Toggle overflow Delete all
catopology segments that involve the restored server.ipa topologysegment-del
[root@server ~]# ipa topologysegment-delCopy to Clipboard Copied! Toggle word wrap Toggle overflow Suffix name: ca Segment name: ca_segment ----------------------------- Deleted segment "ca_segment" -----------------------------
Suffix name: ca Segment name: ca_segment ----------------------------- Deleted segment "ca_segment" -----------------------------Copy to Clipboard Copied! Toggle word wrap Toggle overflow
- The servers affected by the data loss must be abandoned. To create replacement replicas, see Recovering multiple servers with replication.
7.2. Responding to limited data loss among all servers Copy linkLink copied to clipboard!
Respond to known, limited data loss that has propagated to all replicas, such as an accidental deletion. You can manually re-add the missing information to the database using a backup or a Virtual Machine (VM) snapshot.
Prerequisites
- A Virtual VM snapshot or IdM backup of an IdM server that contains the lost data.
Procedure
- If you need to review any lost data, restore the VM snapshot or backup to an isolated server on a separate network.
-
Add the missing information to the database using
ipaorldapaddcommands.
7.3. Responding to undefined data loss among all servers Copy linkLink copied to clipboard!
Respond to severe or unknown data loss that has affected every replica in the deployment. You can restore an Identity Management (IdM) Certificate Authority (CA) server from a Virtual Machine (VM) snapshot to a known good state and use it to deploy an entirely new environment.
Prerequisites
- A VM snapshot contains the lost data.
Procedure
- Restore an IdM Certificate Authority (CA) Replica from a VM snapshot to a known good state, and deploy a new IdM environment from it. See Recovering from only a VM snapshot.
-
Add any data created after the snapshot was taken using
ipaorldapaddcommands.