Managing Serviceguard A.11.20, March 2013

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.)
Creating a Storage Infrastructure with Veritas Cluster File System (CFS)
NOTE: Check the Serviceguard/SGeRAC/SMS/Serviceguard Manager Plug-in Compatibility
and Feature Matrix and the latest Release Notes for your version of Serviceguard for up-to-date
information about support for CFS (and CVM - Cluster Volume Manager) at http://www.hp.com/
go/hpux-serviceguard-docs.
This section provides information about configuring a cluster that uses the Veritas cluster file system
(CFS) with Veritas cluster volume manager (CVM) 4.1 and later. Serviceguard enables you to
create and manage disk groups and mount points using modular style packages or legacy style
packages using CFS. However, creation and administration of modular CFS packages is supported
with CVM 5.0.1 HP Serviceguard CFS A.11.20 April 2011 patch (PHSS_41674) or later. Both
legacy CFS packages and modular CFS packages can co-exist in the same cluster. Configure
CVM/CFS after you configure the cluster. Do not configure applications as a part of modular style
CVM disk groups, CFS mount points, check point, or snapshot packages. The Veritas volume
manager includes a Java-based GUI, known as the Veritas Enterprise Administrator (VEA). You
can create legacy CFS packages using the cfs commands or using VEA. To create modular CFS
packages, use the cmmakepkg command. Serviceguard Manager can also be used to create
modular CFS packages. For details on how to create modular CFS packages in Serviceguard
Manager, see the Serviceguard Manager online help.
Modular CFS packages v/s Legacy CFS packages
The following list helps you understand the difference between modular CFS packages and legacy
CFS packages:
Table 9 Differences between Legacy CFS and Modular CFS
ModularLegacy
Unlike the legacy CFS packages, the modular CVM disk
groups and CFS mount points cannot be created or managed
The CFS legacy disk groups and mount points can be
created or managed only by using the cfsdgadm,
cfsmntadm, cfsmount, or cfsumount.
by using the cfs commands. These are created and managed
using cmmakepkg, cmcheckconf, cmapplyconf,
Legacy CFS packages can be created using the Veritas
Enterprise Administrator (VEA).
cmdeleteconf, cmrunpkg, cmhaltpkg, or cmmodpkg
commands.
Modular CFS packages can be created using Serviceguard
Manager.
Multiple disk groups and mount points can be consolidated
into a single package. This significantly reduces the number
Each package can only correspond to one disk group
or one mount point leaving fewer packages for other
of packages used, leaving more packages for otherpurposes, so if you have many packages they may take
a longer time for startup, shutdown, cmviewcl, etc. applications, thus improving the overall system performance
for startup, shutdown, cmviewcl, etc.
Multiple checkpoints and snapshots can also be merged into
individual modular checkpoint and snapshot packages. See
“Guidelines for Migrating from Legacy CFS Package to
Modular CFS Package” (page 218) for recommendation.
204 Building an HA Cluster Configuration