Recovering from a disaster

Assumptions about your cluster

The following section assumes that you created a mirrored cluster with the following configuration:

The local and partner nodes are in separate physical locations.
Clustering and Local SyncMirror are licensed on both nodes.
Remote SyncMirror is licensed and running on both nodes, prior to the disaster.
The root volume is mirrored with one plex at each site and data volumes are mirrored with one plex at each site.

You might encounter the following types of disasters:

To recover from a disaster, complete the following steps.

Note
You need the Data Protection Guide to help you complete this procedure.

Step	Action
1	Isolate the partner node (node at disaster site) by powering it off. If you cannot physically turn off that node, isolate it by manually isolating (fencing) it, as described in the Data Protection Guide.
2	If...	Then...
	The local and partner nodes can access their local data, but cannot access or communicate with each other or their remote storage	Restore access by replacing or reconnecting the damaged or missing cables. Note Do not force a takeover of the partner. Confirm access to the remote storage by using the following command: `sysconfig -v` Confirm connection between the local and partner node, using the following command: `cf monitor` Complete the disaster recovery procedures, as described in the Data Protection Guide.
	The remote node and storage are physically damaged or failed	Force the takeover of the partner node by using the following command: `cf forcetakeover -d` Replace equipment and cabling, as needed. Contact Customer Support for assistance. Complete the disaster recovery procedures, as described in the Data Protection Guide.