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

The following procedure details how to validate the VERITAS disk groups on nodes in the target
disk site:
1. Login to the target disk site's 3PAR storage system. Stop the Remote Copy volume group and
reverse the direction of replication.
cli% setrcopygroup reverse -stopgroups <rc_volume_group_name>
2. Import the disk group on a node in the target disk site.
# vxdg -tfC import logdata
3. Start the logical volume in the disk group.
# vxvol -g logdata startall
4. Create a directory to mount the volume.
# mkdir /logs
5. Mount the volume.
# mount /dev/vx/dsk/logdata/logfile /logs
6. Verify if the file system is present, and then unmount the file system.
# umount /logs
7. Deport the disk group.
# vxdg deport logdata
Repeat steps 2 through 7 on all nodes in the cluster that require access to this disk group.
8. Login to the source disk site's 3PAR storage system. Reverse the direction of replication to
bring it back to its original direction.
cli% setrcopygroup reverse <rc_volume_group_name>
cli% startrcopygroup <rc_volume_group_name>
Configuring Modular Packages
A Metrocluster must be completed using Metrocluster 3PAR module dts/mc3parrc.
NOTE: The maximum number of Metrocluster packages that can be configured is 16. For more
information, see “Managing SSH connections to 3PAR array” (page 335).
Perform the following steps on a node in a Metrocluster to configure a modular package using the
Metrocluster 3PAR module:
1. Run the following command to create a modular package configuration file using the
Metrocluster with 3PAR Remote Copy module dts/mc3parrc.
# cmmakepkg –m dts/mc3parrc pkgName.config
In this command, dts/mc3parrc is the Metrocluster with 3PAR Remote Copy module that needs
to be included to create a Metrocluster with 3PAR Remote Copy package configuration file.
By default, the mc3parrc module includes only the Serviceguard volume group module.
If modules other than the Serviceguard modules need to be included, they need to be explicitly
specified while creating the Metrocluster with 3PAR Remote Copy modular package
configuration file.
The following example shows the package IP, the filesystem, and the monitor subnet module
included along with the mc3parrc module.
# cmmakepkg –m dts/mc3parrc –m sg/filesystem –m sg/monitor_subnet
-m sg/package_ip temp.config
322 Building Disaster Recovery Serviceguard Solutions Using Metrocluster with 3PAR Remote Copy