Building Disaster Recovery Serviceguard Solutions Using Metrocluster with 3PAR Remote Copy

2 Configuring an application in a Metrocluster environment
Installing the necessary software
Before a Metrocluster can be configured, make sure the following software is installed on all nodes:
Serviceguard
Metrocluster with 3PAR Remote Copy
MCDR Enabler Toolkit
For more information on the software, see the Metrocluster with 3PAR Remote Copy Release Notes
and Serviceguard Disaster Recovery Products Compatibility and Feature Matrix (Metrocluster with
3PAR Remote Copy) available at http://www.hp.com/go/hpux-serviceguard-docs -> HP
Metrocluster with 3PAR Remote Copy.
Creating the cluster
Create the cluster or clusters according to the process described in the Managing Serviceguard
manual available at http://www.hp.com/go/hpux-serviceguard-docs. In the case of a Metrocluster,
create a single Serviceguard cluster with components on multiple sites.
NOTE: Do not configure a 3PAR Remote Volume group volume, Primary or Secondary, as a
cluster lock disk. A cluster lock disk must always be writable. The volumes of a Remote Copy volume
group might not always be writable, therefore none of them can be used as a cluster lock disk. A
configuration with a cluster lock disk that is part of a remote copy volume group is not a supported
configuration.
Site Aware failover configuration
To use either of these package failover policies : site_preferred_manual or
site_preferred, the underlying cluster must be configured with sites and each cluster node
must be associated to a site. The Serviceguard cluster configuration file includes the following
attributes to define sites:
Table 1 Serviceguard cluster configuration file attributes
DefinitionAttributes
To define a unique name for a site in the cluster.SITE_NAME
To associate a node to a site, specify the site name using the SITE keyword
under the node's NODE_NAME definition.
SITE
The following is a sample of the site definition in a Serviceguard cluster configuration file:
SITE_NAME san_francisco
SITE_NAME san_jose
NODE_NAME SFO_1
SITE san_francisco
.....
NODE_NAME SFO_2
SITE san_francisco
........
NODE_NAME SJC_1
SITE san_jose
.......
NODE_NAME SJC_2
SITE san_jose
........
Installing the necessary software 11