Understanding and Designing Serviceguard Disaster Recovery Architectures

Figure 20 Integrity VM or vPars as a Serviceguard Package in Continentalclusters
Node 1
Node 2
Continentalclusters
Primary Cluster
Recovery Cluster
Recovery Group
Replication Link
XP Arrays
Node 3 Node 4
XP Arrays
Indicates that package is running.
Indicates that package is halted.
ccmonpkg
Read/Write Write Disabled
LAN/WAN
HPVM
Pri-Pkg
HPVM
Rec-Pkg
Virtualized Environments as a Serviceguard Node in a Metrocluster or
Continentalclusters
In this model, the virtual partitions or the Integrity virtual machines are configured as Serviceguard
cluster nodes. The following configurations are supported in this model:
• Virtual Partitions/Integrity VM on Separate Hosts
• Multiple Virtual Partitions/Integrity VM on a Single Host
• Combination of Physical Hosts and Virtual Partitions/Integrity VM
• Combination of any of the above
HP recommends and in some cases it is mandatory for the virtual partitions or the Integrity VM
guests be configured with NPIV FC devices. Table 2 lists the products wherein NPIV configuration
is mandatory. Using NPIV ensures that only guests have exclusive access to the storage disks.
Without NPIV the disks needs to be presented to the hosts first, and then assigned to the guests.
So, there is a possibility of data corruption when both hosts and guests inadvertently try to access
the same disks.
NOTE: If disks are not presented using NPIV, you must not present logical volumes (LVM) of the
physical host as disks to the guest. Instead, add the physical disks directly to the guests.
Table 2 Metrocluster dependency with NPIV
Is NPIV Mandatory ?Product
YesMetrocluster with Continuous Access XP and P9000
NoMetrocluster with Continuous Access EVA
44 Metrocluster and Continentalclusters