Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access EVA A.05.01

NOTE: Exclusive activation must be used for all volume groups associated with packages that
use EVA. In Metrocluster with Continuous Access EVA, only one node will have a Volume Group
activated at any given 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 /opt/cmcluster/toolkit/SGCAEVA/Samples/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
NOTE: If you are using the March 2008 version or later of HP-UX 11i v3, skip step 1;
vgimport (1m) will create the device file.
2. Import the Volume Groups on all nodes at the remote 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. To verify the Volume Group configuration, do the following:
• To failover the DR group, follow the steps in HP P6000 Command view as shown in
Figure 4
a. Select the remote storage system from the HP P6000 Command View.
b. Select the desired Disaster Recovery group, and then click Fail Over. This makes the
destination VDisks as SOURCE.
4. Activate the Volume Group and back up the configuration.
# vgchange -a e /dev/<vgname>
# vgcfgbackup /dev/<vgname>
See the sample script /opt/cmcluster/toolkit/SGCAEVA/Samples/mk2imports.
5. Deactivate the Volume Groups.
# vgchange -a n /dev/<vgname>
6. To failover the DR group, follow the steps in HP P6000 Command view as shown in Figure 4
a. Select the local storage system from the HP P6000 Command View.
b. Select the desired Disaster Recovery group and click on “Fail Over”. This will revert the
state of local VDisks to SOURCE.
24 Configuring an application in a Metrocluster environment