Veritas Volume Manager 5.0.1 Administrator's Guide, HP-UX 11i v3, First Edition, November 2009

each disk is known by the same name to VxVM for all of the paths over which it
can be accessed. For example, the disk device enc0_0 represents a single disk for
which two different paths are known to the operating system, such as sdf and
sdm.
See “Disk device naming in VxVM” on page 77.
See “Changing the disk-naming scheme” on page 98.
To take account of fault domains when configuring data redundancy, you can
control how mirrored volumes are laid out across enclosures.
See “Mirroring across targets, controllers or enclosures” on page 296.
Virtual objects
VxVM uses multiple virtualization layers to provide distinct functionality and
reduce physical limitations.
Virtual objects in VxVM include the following:
■ Disk groups
See “Disk groups” on page 31.
■ VM disks
See “VM disks” on page 32.
■ Subdisks
See “Subdisks” on page 33.
■ Plexes
See “Plexes” on page 34.
■ Volumes
See “Volumes” on page 35.
The connection between physical objects and VxVM objects is made when you
place a physical disk under VxVM control.
After installing VxVM on a host system, you must bring the contents of physical
disks under VxVM control by collecting the VM disks into disk groups and
allocating the disk group space to create logical volumes.
To bring the physical disk under VxVM control, the disk must not be under LVM
control.
For more information on how LVM and VM disks co-exist or how to convert LVM
disks to VM disks, see the Veritas Volume Manager Migration Guide.
29Understanding Veritas Volume Manager
How VxVM handles storage management