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

8. Use the vgexport command with the -p option to export the Volume Groups on the primary
system without removing the HP-UX device files.
# vgexport -s -p -m mapfile /dev/vgname
Make sure that you copy the map files to all of the nodes. The sample script Samples/ftpit
shows a semi-automated way (using ftp) to copy the files. It is necessary to only enter the
password interactively.
9. De-activate the volume group.
# vgchange -a n /dev/vgname
Configuring Volume Groups using PVLinks
Use the following steps to create volume groups for source volumes using PVLinks and export them
for access by other nodes.
NOTE: Create volume groups only for source storage on a locally connected EVA unit. To create
volume groups for source volumes on EVA unit located at the remote site, it is necessary to log
onto a node located at that site before configuring the volume groups.
1. Define the appropriate Volume Groups on each node that run the application package with
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.
2. Create the Volume Groups on the source volume, which uses PVLink for path failover. All the
special device files names associated for the vdisk as identified in the section “Identifying
Special Device Files for PVLinks Configuration”.
The following commands are an example of how VG using Pvlink is created for the vdisk
identified by WWN 6005-08b4-0010-203d-0000-6000-0017-0000:
# pvcreate -f /dev/rdsk/c16t0d1
# vgcreate /dev/vgname /dev/dsk/c16t0d1
# vgextend /dev/vgname /dev/dsk/c17t0d1
# vgextend /dev/vgname /dev/dsk/c18t0d1
# vgextend /dev/vgname /dev/dsk/c20t0d1
# vgextend /dev/vgname /dev/dsk/c12t0d1
# vgextend /dev/vgname /dev/dsk/c13t0d1
# vgextend /dev/vgname /dev/dsk/c14t0d1
# vgextend /dev/vgname /dev/dsk/c15t0d1
3. De-activate the Volume Groups.
# vgchange -a n /dev/vgname
4. Start the cluster and configure the Volume Groups.
# cmruncl (if cluster is not already up and running)
# vgchange -c y /dev/vgname
5. Test the Volume Groups activation with exclusive option.
# vgchange -a e/dev/vgname
6. Create a back-up conffile that will contain the cluster ID, already having an ID on disks/
luns.
# vgcfgbackup /dev/vgname
7. Use the vgexport command with the-p option to export the Volume Groups on the primary
system without removing the HP-UX device files.
# vgexport -s -p -m mapfile /dev/vgname
228 Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access EVA