VERITAS Volume Manager 4.1 Release Notes (5900-0591, March 2010)

VERITAS Volume Manager 4.1 Release Notes
VERITAS Base-VXVM 4.1 Licenses
Chapter 1 17
VEA Graphical User Interface and SAM
The VERITAS Enterprise Administrator (VEA) provides a Java-based graphical user
interface for managing Base-VXVM. VEA has two parts: a server and a client. The server
must run on the system running Base-VXVM. The client can run on the server machine, or
the client software can be installed on a different HP-UX 11i version 2 system to manage
Base-VXVM remotely. Note that only HP-UX 11i clients are supported.
SAM, the HP-UX system administration manager, and VEA exist as independent entities.
The VEA client can and should be launched from SAM. SAM is used to manage LVM objects
and the VEA is used to manage VxVM objects. However, VEA recognizes and labels LVM
volumes and disks, and similarly, SAM recognizes and labels VxVM volumes and disks. To
manage VxVM disks graphically, you must use VEA. For information about VEA, see the
VERITAS Enterprise Administrator (VEA 500 Series) Getting Started guide.
WARNING System Administration Manager (SAM) does not recognize a VxFS 4.1
file system with Disk Layout Version 6.
Coexistence with HP Logical Volume Manager (LVM)
The VERITAS Volume Manager for HP-UX coexists with HP Logical Volume Manager (LVM).
Before Base-VXVM 4.1, the VERITAS Volume Manager could not be used to control the
root/boot disk.
Both LVM and Base-VXVM utilities are aware of the other volume manager, and will not
overwrite disks that are being managed by the other volume manager. As mentioned above,
the administrative utilities (SAM and VEA) recognize and identify all disks on the system.
Although this release is targeted at new customer installations, a conversion utility,
vxvmconvert, is provided for converting LVM volume groups to VxVM volume groups. Refer
to the VERITAS Volume Manager 4.1 Migration Guide for details on using vxvmconvert.