Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access for P9000 and XP A.11.00

Notes on the Raid Manager configuration
• A single P9000 or XP device group must be defined for every package on every host that is
connected to the P9000 or XP series disk array.
• Device groups are defined in the Raid Manager configuration file under the heading
HORCM_DEV or HORCM_LDEV.
• The disk target IDs and LUNs for all Physical Volumes (PVs) defined in Volume Groups (VGs)
or disk groups (DGs) that belong to the package must be defined in one P9000 or XP device
group on every host system that might run one or more Metrocluster packages.
• The device group name (dev_group) is user-defined and must be the same on every host in
the Metrocluster that accesses the P9000 or XP disk array. The device group name (dev_group)
must be unique within the cluster; it must be a name that is easily associated with the application
name or Serviceguard package name.
• The TargetID and LU# fields for every device name might be different on different hosts in the
clusters, to allow for different hardware I/O paths on different hosts.
Configuring automatic Raid Manager startup
After editing the Raid Manager configuration files and installing them on the nodes that are attached
to the P9000 or XP Series disk arrays, you must configure automatic Raid Manager startup on the
same nodes. This is done by editing the rc script /etc/rc.config.d/raidmgr. Set the
START_RAIDMGR parameter to 1, and define RAIDMGR_INSTANCE as the number of the Raid
Manager instances being used. By default, this is zero (0).
See “Sample file for configuring automatic Raid Manager startup” (page 182) for a sample edited
configuration file for XP Raid Manager Instance.
Configuring LVM volume group and VxVM disk group
Both LVM and Veritas VxVM storage can be used in disaster tolerant clusters. The following sections
show how to set up every type of volume group.
Creating and exporting LVM volume groups using Continuous Access P9000 or XP
To create and export volume groups:
1. Define the appropriate Volume Groups on every node that might run the application package.
Use the following commands:
# mkdir /dev/<vgname>
# mknod /dev/<vgname>/group c 64 0xnn0000
where the name /dev/<vgname> and the number nn are unique within the cluster.
NOTE: If you are using HP-UX 11i v3 March 2008 version or later, you can skip step 1;
vgcreate (1m) creates the device file.
2. Create the volume group on the source volume.
# pvcreate -f /dev/rdisk/disk12
# vgcreate /dev/<vgname> /dev/disk/disk12
NOTE: If you are using LVM PVLinks, add all the paths of the disk to the volume group by
using the following command:
# vgextend /dev/<vgname> /dev/disk/disk13
3. Create the logical volume (XXXX indicates size in MB).
# lvcreate -L XXXX /dev/<vgname>
Configuring LVM volume group and VxVM disk group 23