NOTE: Use the vgimport -Ncommand to configure the volume group using agile DSF. In the absence of the -Noption, legacy DSF is used.

3.Verify the Volume Group configuration with the following procedures:

•From the command view EVA, shown in Figure 38 failover the DR group to make it the source on the REMOTE site instead of the destination by following the steps described below:

a.Select the destination site storage system from the command view EVA.

b.Next select the desired Disaster Recovery group and click on “Fail Over”.

4.Activate the Volume Groups and back up the configuration.

# vgchange -a e /dev/vgname

# vgcfgbackup /dev/vgname

See the sample script Samples/mk2imports.

5.De-activate the Volume Groups.

# vgchange -a n /dev/vgname

6.From the command view EVA, failback the SOURCE to its original site.

Figure 38 EVA Command View DR Group Properties

Building a Metrocluster Solution with Continuous Access EVA

Configuring Legacy Packages for Automatic Disaster Recovery

After completing the following steps, packages will be able to automatically fail over to an alternate node in another data center and still have access to the data that they need in order to operate.

Customizations include editing an environment file to set environment variables, and customizing the package control script to include customer-defined run and halt commands, as appropriate. The package control script must also be customized for the particular application software that it will control. Consult the Managing Serviceguard user’s guide for more detailed instructions on how to start, halt, and move packages and their services between nodes in a cluster. For ease of troubleshooting, configure and test one package at a time.

1.Create a directory /etc/cmcluster/<package_name> for each package:

#mkdir /etc/cmcluster/<package_name>

2.Create a package configuration file.

#cd /etc/cmcluster/<package_name>

#cmmakepkg -p <package_name>.config

Building a Metrocluster Solution with Continuous Access EVA 231