Building Disaster Recovery Serviceguard Solutions Using Metrocluster with EMC SRDF

/dev/vx/dsk/cvm_dg0/lvol2”
service_restart none
service_fail_fast_enabled no
service_halt_timeout 300
Easy deployment of Metrocluster modular packages
Starting with Serviceguard version A.11.20, the Package Easy Deployment feature is introduced.
This feature is available from the Serviceguard Manager version B.03.10 onwards. It provides a
simple way to quickly deploy Metrocluster modules in supported toolkit applications. For detailed
information about the Package Easy Deployment feature, see Using Easy Deployment in Serviceguard
and Metrocluster Environments available at http://www.hp.com/go/hpux-serviceguard-docs —>
HP Serviceguard.
The advantage offered by the Package Easy Deployment feature is that you need not enter any of
the Metrocluster module parameters in the modular package configuration file. The appropriate
Metrocluster module along with proper values for its parameters is automatically inserted into the
package configuration file based on the type of disks used by the supported toolkit application.
If the disks are EMC SRDF disks, and are replicated, then the dts/mcsrdf module is automatically
inserted into the package configuration file.
The following dts/mcsrdf parameters are auto-discovered:
• DEVICE_GROUP
• RDF_MODE
• CONSISTENCYGROUPS
The following prerequisites and limitations are applicable to the package easy deployment for
Metrocluster with EMC SRDF.
Prerequisite
The Device Group or the Consistency Group must be created.
Limitations
If the enclosure based naming scheme is used by Veritas Volume manager, the package easy
deployment feature of Metrocluster packages is not supported.
Some further points
Following are some of the requirements specific to EMC Symmetrix:
• R1 and R2 devices must be correctly defined and assigned to the appropriate nodes in the
internal configurations that is downloaded by EMC support staff.
• R1 devices are locally protected (RAID 1 or RAID S); R2 devices are locally protected (RAID
1, RAID S or BCV).
NOTE: HP recommends that the R2 device is locally protected with RAID 1 or RAID S. If
the R2 device is protected with BCV, and if it fails, and there is a failover, then the package
cannot operate on the BCV device. In such a situation, the R2 device must be fixed, and the
data must be restored from the BCV device to the new R2 device before the package can
start.
• Only synchronous and asynchronous modes are supported; adaptive copy must be disabled.
Some further points 35