Managing Serviceguard 11th Edition, Version A.11.16, Second Printing June 2004

Building an HA Cluster Configuration
Creating a Storage Infrastructure with VxVM
Chapter 5 209
Creating a Storage Infrastructure with VxVM
In addition to configuring the cluster, you create the appropriate logical
volume infrastructure to provide access to data from different nodes.
This is done with Logical Volume Manager (LVM), VERITAS Volume
Manager (VxVM), or VERITAS Cluster Volume Manager (CVM). You
can also use a mixture of volume types, depending on your needs. LVM
and VxVM configuration are done before cluster configuration, and CVM
configuration is done after cluster configuration.
For a discussion of migration from LVM to VxVM storage, refer to
Appendix G.
This section shows how to configure new storage using the command set
of the VERITAS Volume Manager (VxVM). Once you have created the
root disk group (described next), you can use VxVM commands or the
Storage Administrator GUI, vmsa, to carry out configuration tasks. If you
are using vmsa, be sure the Storage Administrator server is running
before you launch the GUI. Details are given in the VERITAS Volume
Manager for HP-UX Release Notes. For more information, refer to the
VERITAS VMSA Administrator’s Guide. If you are using commands,
refer to the VxVM man pages.
Initializing the VERITAS Volume Manager
If you are about to create disk groups for the first time, you need to
initialize the Volume Manager. This is done by creating a disk group
known as rootdg that contains at least one disk. Use the following
command once only, immediately after installing VxVM on each node:
# vxinstall
This displays a menu-driven program that steps you through the VxVM
initialization sequence. From the main menu, choose the “Custom”
option, and specify the disk you wish to include in rootdg.
IMPORTANT The rootdg in the VERITAS Volume Manager is not the same as the
HP-UX root disk if an LVM volume group is used for the HP-UX root
disk file system. Note also that rootdg cannot be used for shared storage.
However, rootdg can be used for other local filesystems (e.g.,
/export/home), so it need not be wasted.