Managing Serviceguard 13th Edition, February 2007

Building an HA Cluster Configuration
Configuring the Cluster
Chapter 5230
The cmapplyconf command creates a binary version of the cluster
configuration file and distributes it to all nodes in the cluster. This action
ensures that the contents of the file are consistent across all nodes. Note
that the cmapplyconf command does not distribute the ASCII
configuration file.
NOTE The apply will not complete unless the cluster lock volume group is
activated on exactly one node before applying. There is one exception to
this rule: a cluster lock had been previously configured on the same
physical volume and volume group.
After the configuration is applied, the cluster lock volume group must be
deactivated.
Storing Volume Group and Cluster Lock Configuration Data
After configuring the cluster, create a backup copy of the LVM volume
group configuration by using the vgcfgbackup command for each volume
group you have created. If a disk in a volume group must be replaced,
you can then restore the disk's metadata by using the vgcfgrestore
command. The procedure is described under “Replacing Disks” in the
“Troubleshooting” chapter.
Be sure to use vgcfgbackup for all volume groups, especially the cluster
lock volume group.
NOTE You must use the vgcfgbackup command to store a copy of the cluster
lock disk's configuration data whether you created the volume group
using the System Management Homepage (SMH), SAM, or HP-UX
commands.
If the cluster lock disk ever needs to be replaced while the cluster is
running, you must use the vgcfgrestore command to restore lock
information to the replacement disk. Failure to do this might result in a
failure of the entire cluster if all redundant copies of the lock disk have
failed and if replacement mechanisms or LUNs have not had the lock
configuration restored. (If the cluster lock disk is configured in a disk
array, RAID protection provides a redundant copy of the cluster lock
data. Mirrordisk/UX does not mirror cluster lock information.)