Building Disaster Recovery Serviceguard Solutions Using Metrocluster with 3PAR Remote Copy for Linux B.12.00.00

# pvcreate -f /dev/sda1
2. Create the volume group on the source volume.
# vgcreate --addtag $(uname -n) /dev/<vgname> /dev/sda1
# vgcreate --addtag $(uname -n) /dev/<vgname>
3. Create the logical volume. (XXXX indicates size in MB).
# lvcreate -L XXXX /dev/<vgname>
4. Create a file system on the logical volume.
# mke2fs -j /dev/<vgname>/lvol1
5. If required, deactivate the volume groups on the primary system and remove the tag.
# vgchange -a n <vgname>
# vgchange --deltag $(uname -n) <vgname>
6. Run the vgscan command to make the LVM configuration visible on all the nodes.
# vgscan
7. On the source disk site, run the following commands on all the systems that might run the
Serviceguard package. If required, take a back up of a LVM configuration.
# vgchange --addtag $(uname -n) <vgname>
# vgchange -a y <vgname>
# vgcfgbackup <vgname>
# vgchange -a n <vgname>
# vgchange --deltag $(uname -n) <vgname>
8. If the Remote Copy Volume Group is configured in asynchronous periodic mode, then to reflect
disk group configuration done at the source disk site, you must synchronize the Remote Copy
Volume Group from the 3PAR storage system of the source disk site.
cli% syncrcopy <rc_volume_group_name>
9. Log in to the 3PAR storage system of the target disk site. Stop the Remote Copy Volume Group
and reverse the direction of replication to make disks read/write.
cli% setrcopygroup reverse —stopgroups <rc_volume_group_name>
10. On the target disk site, run the following commands on all the systems that might run the
Serviceguard package. If required, take a back up of a LVM configuration.
# vgchange --addtag $(uname -n) <vgname>
# vgchange -a y <vgname>
# vgcfgbackup <vgname>
# vgchange -a n <vgname>
# vgchange --deltag $(uname -n) <vgname>
11. Login to the source disk site of the 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>
If you do not want to suspend replication at this point of time, skip the step 8, 9 and 10.
However, this will not activate the volume group to perform the vgcfgbackup. Perform the
vgcfgbackup when the volume group is activated during the first package startup at the
target disk site.
16 Configuring an application in a Metrocluster environment