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

IMPORTANT: 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, mass storage on HP-UX,
DSF migration and LVM Online Disk Replacement, see the following documents that are available
at http://www.hp.com/go/hpux-serviceguard-docs
• LVM Migration from Legacy to Agile Naming Model
• HP-UX 11i v3 Mass Storage Device Naming
• Serviceguard Migration
• LVM Online Disk Replacement
Importing Volume Groups on Nodes at the Same Site
Use the following procedure to import volume groups on cluster nodes located at the same site as
the EVA on which you are doing the Logical Volume Manager configuration. The sample script
mk2imports can be modified to automate these steps.
NOTE: Before running vgimport, it is necessary to create the directory under the /dev directory
and create the group file.
1. Define the Volume Groups on all nodes at the same site that will run the Serviceguard package.
# mkdir /dev/vgname
# mknod /dev/vgname/group c 64 0xnn0000
2. Import the Volume Groups on all nodes at the same site that will run the Serviceguard packages.
# vgimport -vs -m mapfile /dev/vgname
NOTE: Use the vgimport -N command to configure the volume group using agile DSF.
In the absence of the -N option, legacy DSF is used.
3. Activate the Volume Groups and back up the configuration.
# vgchange -a e /dev/vgname
# vgcfgbackup /dev/vgname
See the sample script Samples/mk2imports.
4. De-activate the Volume Groups.
# vgchange -a n /dev/vgname
NOTE: Exclusive activation must be used for all volume groups associated with packages that
use EVA. The design of Metrocluster Continuous Access EVA assumes that only one node in the
cluster will have a Volume Group activated at a time.
Importing Volume Groups on Nodes at the Remote Site
Use the following procedure to import volume groups on all cluster nodes located at the site of the
remote EVA. The sample script mk2imports can be modified to automate these steps.
1. Define the Volume Groups on all nodes at the remote site that will run the Serviceguard
package.
# mkdir /dev/vgname
# mknod /dev/vgname/group c 64 0xnn0000
2. Import the Volume Groups on all nodes at the remote site that will run the Serviceguard
packages.
# vgimport -vs -m mapfile /dev/vgname
230 Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access EVA