Managing Serviceguard Seventeenth Edition, First Reprint December 2009

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: _____________________________________________________

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:

• CVM disk groups are created after the cluster is configured, whereas VxVM disk

groups may be created before cluster configuration if desired.

• High availability applications, services, and data should be placed in separate disk

groups from non-high availability applications, services, and data.

• You must not group two different high availability applications, services, or data,

whose control needs to be transferred independently, onto the same disk group.

• Your HP-UX root disk can belong to an LVM or VxVM volume group that is not

shared among cluster nodes.

• A cluster lock disk must be configured into an LVM volume group; you cannot

use a VxVM or CVM disk group. (See “Cluster Lock Planning” (page 129) for

information about cluster lock options.)

• VxVM disk group names should not be entered into the cluster configuration file.

These names are not inserted into the cluster configuration file by cmquerycl.

CVM and VxVM Planning 133