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

<node1> <node2>
In this command, <node1> and <node2> are nodes in the primary cluster.
4. Activate the CVM disk group in the primary cluster CFS sub-cluster.
# cfsdgadm activate <cvm_dg_name>
5. Create a volume from the disk group.
# vxassist -g <cvm_dg_name> make \
<cvm_dg_vol_name> 4500m
Configuring the Storage Device using VERITAS CVM
Complete the following procedure on the CVM cluster master node in the primary cluster to setup
the CVM disk group volumes:
1. Initialize the source disks of the replication pair.
# /etc/vx/bin/vxdisksetup -i <replicated_disk_1>
# /etc/vx/bin/vxdisksetup -i <replicated_disk_2>
2. Create a disk group for the complex workload data.
# vxdg –s init <cvm_dg_name> <replicated_disk_1>\
<replicated_disk_2>
3. Activate the CVM disk group on all the nodes in the primary cluster CVM sub-cluster.
# vxdg -g <cvm_dg_name> set activation=sw
4. Create a volume from the disk group.
# vxassist -g <cvm_dg_name> make \
<cvm_dg_vol_name> 4500m
5. Create Serviceguard Disk Group modular MNP packages for the disk group.
IMPORTANT: VERITAS CVM disk groups must be configured as a dedicated modular MNP
package using the cvm_dg attribute. This modular MNP package must be configured to have a
package dependency on the SG-CFS-pkg SMNP package. Continentalclusters with SADTA does
not support configuring Legacy style packages for managing VERITAS CVM disk groups.
Complete the following steps to create a Modular package for a CVM disk group:
1. Create a package configuration file using the following modules:
# cmmakepkg -m sg/multi_node -m sg/dependency -m\
sg/resource -m sg/volume_group <cvm_dg_pkg_name>.conf
2. Edit the configuration file and specify values for the following attributes as below:
package_name <cvm_dg_pkg_name>
package_type multi_node
cvm_dg <cvm_dg_name>
cvm_activation_cmd "vxdg -g \${DiskGroup}
set activation=sharedwrite"
3. Specify the nodes in the primary cluster using the node_name attribute:
node_name <node1>
node_name <node2>
In this command, <node1> and <node2> are nodes in the primary cluster.
Support for Complex Workloads in a Continentalclusters Environment using SADTA 131