Building Disaster Recovery Serviceguard Solutions Using Metrocluster with EMC SRDF

package_name <siteB_cfs_pkg_name>
cvm_disk_group <cvm_dg_name>
cvm_activation_mode "node3=sw node4=sw"
cfs_mount_point <cvm_mount_point>
cfs_volume <cvm_dg_name>/<cvm_dg_vol_name>
cfs_mount_options "node3=cluster node4=cluster"
cfs_primary_policy ""
where node3 and node4 are the nodes at the target disk site.
Do not configure any mount specific attributes such as cfs_mount_point and
cfs_mount_options if SG SMS CVM is configured as raw volumes.
4. Verify the package configuration file.
# cmcheckconf -P cfspkg1.ascii
5. Apply the package configuration file.
# cmapplyconf -P cfspkg1.ascii
6. Run the package.
# cmrunpkg <siteB_cfs_pkg_name>
Configuring the storage device using Veritas CVM
To import CVM disk groups on the nodes in the target disk site and to create Serviceguard CVM
disk group package:
1. From the CVM master node at the target disk site, import the disk groups used by the complex
workload.
# vxdg -stfC import <cvm_dg_name>
2. Create Serviceguard disk group modular MNP packages for the CVM disk group.
IMPORTANT: Veritas CVM disk groups must be configured in a dedicated modular multi-node
package using the cvm_dg attribute. This modular MNP package must be configured to have a
package dependency on the SG-CFS-pkg system multi-node package.
Metrocluster SADTA does not support configuring Legacy style packages for managing Veritas
CVM disk groups.
Configuring the storage device using SLVM
To import volume groups on the nodes in the target disk site:
NOTE: If you are using HP-UX 11i v3 March 2008 version or later, you can skip step 2;
vgcreate (1m) will create the device file for you.
1. Define the appropriate volume groups on each host system in the target disk site:
# mkdir /dev/<vg_name>
# mknod /dev/<vg_name>/group c 64 0xnn0000
where the name /dev/<vg_name> and the number nn are unique within the cluster.
2. Export the volume groups on the source disk site without removing the special device files.
# vgchange -a n <vg_name>
# vgexport -s -p -m <map_file_name> <vg_name>
Ensure that the map files are copied to all the nodes in the target disk site.
3. On the target disk site, import the VGs on all the systems that will run the Serviceguard complex
workload package.
# vgimport -s -m <map_file_name> <vg_name>
44 Configuring complex workloads using SADTA