Managing Serviceguard Sixteenth Edition, March 2009
Physical Volume Name: ____________/dev/dsk/c2t2d0__________________________
Physical Volume Name: ____________/dev/dsk/c3t2d0__________________________
Physical Volume Name: _____________________________________________________
Physical Volume Name: _____________________________________________________
Physical Volume Name: _____________________________________________________
Physical Volume Name: _____________________________________________________
Name of Second Physical Volume Group: _______bus1____________________________
Physical Volume Name: ______________/dev/dsk/c4t2d0________________________
Physical Volume Name: ______________/dev/dsk/c5t2d0________________________
Physical Volume Name: ______________/dev/dsk/c6t2d0________________________
Physical Volume Name: _____________________________________________________
Physical Volume Name: _____________________________________________________
Physical Volume Name: _____________________________________________________
Physical Volume Name: _____________________________________________________
Physical Volume Name: _____________________________________________________
CVM and VxVM Planning
You can create storage groups using the HP-UX Logical Volume Manager (LVM,
described in the previous section), or using Veritas VxVM and CVM software.
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 on CVM support: http://www.docs.hp.com ->High
Availability -> Serviceguard.
When designing a storage configuration using CVM or VxVM disk groups, consider
the following:
• You must create a rootdg disk group on each cluster node that will be using
VxVM storage. This is not the same as the HP-UX root disk, if an LVM volume group
is used. The VxVM root disk group can only be imported on the node where it is
created. This disk group is created only once on each cluster node.
NOTE: The VxVM rootdg is only required for VxVM 3.5 and earlier; it is not
required for VxVM 4.1 and later.
• CVM disk groups are created after the cluster is configured, whereas VxVM disk
groups may be created before cluster configuration if desired.
CVM and VxVM Planning 135