Building Disaster Recovery Serviceguard Solutions Using Metrocluster with 3PAR Remote Copy

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:
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 Source Disk Site using the node_name attribute:
node_name <node1>
node_name <node2>
where node1 and node2 are the nodes in the Source Disk Site.
4. Specify the Serviceguard dependency:
dependency_name SG-CFS-pkg_dep
dependency_condition SG-CFS-pkg=up
dependency_location same_node
5. Apply the newly created package configuration.
# cmapplyconf -v -P <cvm_dg_pkg_name>.conf
Configuring the storage device using SLVM
To create volume groups on the Source Disk Site:
NOTE: If you are using the March 2008 version or later of HP-UX 11i v3, skip step 1; vgcreate
(1m) will create the device file.
1. Define the appropriate volume groups on each host system in the Source 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 entire cluster.
2. Create the volume group on the source volumes.
# pvcreate -f /dev/rdsk/cxtydz
# vgcreate /dev/<vg_name> /dev/dsk/cxtydz
3. Create the logical volume for the volume group:
# lvcreate -L XXXX /dev/<vg_name>
where XXXX indicates the size in MB.
4. Export the volume groups on the primary system without removing the special device files.
# vgchange -a n <vg_name>
# vgexport -s -p -m <map_file_name> <vg_name>
Make sure that you copy the mapfiles to all host systems.
5. On the nodes in the source disk site, import the volume group.
# vgimport -s -m <map_file_name> <vg_name>
32 Configuring complex workloads using SADTA