HP Serviceguard Extended Distance Cluster for Linux A.12.00.00 Deployment Guide, March 2014

Table 4 Disaster Scenarios and Their Handling (continued)
Recovery ProcessWhat Happens When This Disaster
Occurs
Disaster Scenario
VxVM disk groups:
As the network and both the mirrored disk sets are
accessible on node N2, and were also accessible
when node N1 failed. Now, you only need to
restore node N1 and you must enable the package
to run on node N1 after it is repaired by running
the following command:
# cmmodpkg -e P1 -n N1
The package (P1) fails over to
another node (N2). This node (N2)
is configured to take over the
package when it fails on node N1.
A package (P1) is running
on a node (N1). Node N1
experiences a failure.
Once you restore power to S1 or restore the FC
links to S1, the corresponding mirror half of S1 is
accessible from node N1.
Now, the disk group has to reattach automatically
to a site S1 and recover. If not, you must manually
reattach a site and recover the disk group:
#vxdg -g diskgroup reattachsite
sitename
#vxrecover –g diskgroup
For more information, see Cluster File System High
Availability 6.0.1 Administrator's Guide – Linux
The package (P1) continues to run
on node N1 with the mirror plex
that consists of only S2.
A package (P1) is running
on a node N1. The package
uses a VxVM mirror across
sites that consists of two
plexes - S1 (local to node
N1) and S2 (local to Node
N2).
Access to S1 is lost from
both nodes, either due to the
power failure to S1 or loss
of FC links to S1.
44 Disaster Scenarios and Their Handling