Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access XP P9000 for Linux B.12.00.00

2 Configuring an application in a Metrocluster environment
Installing the necessary hardware and software
When you complete the following procedures, an adoptive node is able to access the data
belonging to a package after it fails over.
Setting up the storage hardware
1. Before configuring Metrocluster with Continuous Access XP P9000 for Linux, the XP or P9000
arrays must be correctly cabled with redundant paths to every node in the cluster that will run
packages accessing data on the array.
2. Install and configure the hardware components of the XP or P9000 arrays, including disk
arrays, SAN switches, data replication link, and so on.
Every XP or P9000 Series disk array must be configured with redundant Continuous Access
links, each of which is connected to a different LCP or RCP card. To prevent a single point of
failure (SPOF), there must be at least two physical boards in every P9000 and XP for the
Continuous Access links. Every board usually has multiple ports. However, a redundant
Continuous Access link must be connected to a port on a different physical board from the
board that has the primary Continuous Access link. When using bi-directional configurations,
where data center A backs up data center B and data center B backs up data center A, you
must have at least four Continuous Access links, two in every direction. Four Continuous Access
links are also required in uni-directional configurations in which you want to allow failback.
Installing the necessary software
Before you begin any configuration, ensure the following software is installed on all the nodes:
Serviceguard for Linux A.12.00.00
Metrocluster with Continuous Access XP P9000 for Linux
XP/P9000 RAID Manager
See the Release Notes and Compatibility and Feature Matrix available at http://www.hp.com/
go/linux-serviceguard-docs for the required versions and the latest patches available for the above
mentioned software.
Creating the cluster
NOTE: The file /etc/cmcluster.conf contains the mappings that resolve symbolic references
to $SGCONF, $SGROOT, $SGLBIN, etc. used in the pathnames in the following subsections. If
the Serviceguard variables are not defined on your system, then include the file /etc/
cmcluster.conf in your login profile for the root user. For more information on these parameters,
see Understanding the Location of Serviceguard Files and Enabling Serviceguard Command Access
in Managing HP Serviceguard A.12.00.00 for Linux available at http://www.hp.com/go/
linux-serviceguard-docs .
Create a Serviceguard cluster with components on multiple sites according to the process described
in the Managing HP Serviceguard A.12.00.00 for Linux available at http://www.hp.com/go/
linux-serviceguard-docs .
NOTE: A configuration with a Lock Lun is not supported in a Metrocluster environment.
14 Configuring an application in a Metrocluster environment