Managing Serviceguard Sixteenth Edition, March 2009

When designing your disk layout using LVM, you should consider the following:
• The root disk should belong to its own volume group.
• The volume groups that contain high availability applications, services, or data
must be on a bus or busses available to the primary node and all adoptive nodes.
• High availability applications, services, and data should be placed in a separate
volume group from non-high availability applications, services, and data.
• You must group high availability applications, services, and data, whose control
needs to be transferred together, onto a single volume group or series of volume
groups.
• You must not group two different high availability applications, services, or data,
whose control needs to be transferred independently, onto the same volume group.
• Your root disk must not belong to a volume group that can be activated on another
node.
• HP recommends that you use volume group names other than the default volume
group names (vg01, vg02, etc.). Choosing volume group names that represent
the high availability applications that they are associated with (for example,
/dev/vgdatabase will simplify cluster administration).
• Logical Volume Manager (LVM) 2.0 volume groups, which remove some of the
limitations imposed by LVM 1.0 volume groups, can be used on systems running
some recent versions of HP-UX 11i v3 and Serviceguard. Check the Release Notes
for your version of Servicegaurd for details. For more information, see the white
paper LVM 2.0 Volume Groups in HP-UX 11i v3 at docs.hp.com -> 11i v3 ->
LVM Volume Manager.
If you plan to use the EMS HA Disk Monitor, refer to the section on “Rules for Using
EMS Disk Monitor with Serviceguard” in the manual Using High Availability Monitors
at http://docs.hp.com -> High Availability -> Event Monitoring
Service and HA Monitors -> Installation and User’s Guide
LVM Worksheet
You may find a worksheet such as the following useful to help you organize and record
your physical disk configuration. This worksheet is an example; blank worksheets are
in Appendix E (page 419). Make as many copies as you need.
NOTE: Under agile addressing, the physical volumes in the sample worksheet that
follows would have names such as disk1, disk2, etc. See “About Device File Names
(Device Special Files)” (page 107).
=============================================================================
Volume Group Name: __________/dev/vg01__________________________________
Name of First Physical Volume Group: _______bus0___________________________
Physical Volume Name: ____________/dev/dsk/c1t2d0__________________________
134 Planning and Documenting an HA Cluster