LVM Planning

You can create storage groups using the HP-UX Logical Volume Manager (LVM), or using Veritas VxVM and CVM software as described in the next section.

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.
It is recommended 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/vegetables will simplify cluster administration).

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 (B5736-90074) at http://docs.hp.com -> High Availability -> Event Monitoring Service and HA Monitors -> Installation and User’s Guide

LVM Worksheet

The following worksheet will help you organize and record your specific physical disk configuration. This worksheet is an example; blank worksheets are in Appendix F “Blank Planning Worksheets”. Make as many copies as you need. Fill out the worksheet and keep it for future reference.




	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)”.

 =============================================================================
 
    Volume Group Name:      __________/dev/vg01__________________________________
 
			    Name of First Physical Volume Group:  _______bus0___________________________
 
    Physical Volume Name:   ____________/dev/dsk/c1t2d0__________________________
 
    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:   _____________________________________________________

LVM Planning

Technical documentation

» Table of Contents

» Index

LVM Worksheet