VERITAS Volume Manager 3.5 Release Notes (August 2003)

VERITAS Volume Manager™ HP-UX 11i v2 Release Notes
VERITAS VxVM 3.5 Licenses
Chapter 120
NOTE In an active/passive peripheral, LUNs only accept I/O on
one path at any time. In an active/active peripheral, LUNs
accept I/O on either path at any time.
VEA Graphical User Interface and SAM
The VERITAS Enterprise Administrator (VEA) provides a Java-based
graphical user interface for managing VxVM. VEA has two parts: a
server and a client. The server must run on the system running VxVM.
The client can run on the server machine, or the client software can be
installed on a different HP-UX 11i system to manage VxVM remotely.
Note that only HP-UX 11i clients are supported.
SAM, the HP-UX system administration manager, and VEA exist as
independent entities. 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 informationabout VEA, see the VERITAS Volume Manager 3.5
User’s Guide—VEA.
Coexistence with HP Logical Volume Manager (LVM)
The VERITAS Volume Manager for HP-UX coexists with HP Logical
Volume Manager (LVM). Before VxVM 3.5, the VERITAS Volume
Manager could not be used to control the root/boot disk.
Both LVM and 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
3.5 Migration Guide for details on using vxvmconvert.