Designing Disaster Recovery Clusters using Metroclusters and Continentalclusters, Reprinted October 2011 (5900-1881)

SSH public key successfully set!
4. Repeat the steps from 2 to 3 for the other storage system.
5. Repeat the steps from 1 to 4 on all nodes in the cluster.
Defining Storage Units
Both LVM and VERITAS VxVM storage can be used in disaster tolerant clusters. The following
sections show how to set up each type of volume group:
Creating and Exporting LVM Volume Groups
To create and export LVM volume groups:
NOTE: If you are using the March 2008 version or later of HP-UX 11i v3, skip step1; vgcreate
(1m) will create the device file.
Perform the following steps on the source disk site:
1. Define the appropriate Volume Groups on each host system that might run the application
package
# mkdir /dev/vgname
# mknod /dev/vgname/group c 64 0xnn0000
where the name /dev/vgname and the number nn are unique within the entire cluster.
2. Create the Volume Group on the source volumes.
# pvcreate -f /dev/rdisk/disk3
# vgcreate /dev/vgname /dev/disk/disk3
NOTE: From HP-UX 11i v3 onwards, HP recommends that you use agile DSF naming model
for mass storage devices. For more information on the agile view, see the section About Device
File Names (Device Special Files) in the nineteenth edition of Managing Serviceguard document
available at http://www.hp.com/go/hpux-serviceguard-docs.
3. Create the logical volumes for the volume group.
# lvcreate -L XXXX /dev/vgname
where xxxx indicates size in MB.
4. Create the filesystem.
# newfs -F vxfs /dev/vgname/rlvol
5. Deactivate and export the Volume Groups on the primary system without removing the special
device files.
# vgchange -a n <vgname>
# vgexport -s -p -m <mapfilename> <vgname>
Make sure that you copy the mapfiles to all of the host systems.
6. On the source disk site, import the VGs on all of the other systems that might run the
Serviceguard package and backup the LVM configuration.
# vgimport -s -m <mapfilename> <vgname>
# vgchange -a y <vgname>
# vgcfgbackup <vgname>
# vgchange -a n <vgname>
320 Building Disaster Recovery Serviceguard Solutions Using Metrocluster with 3PAR Remote Copy