Veritas Volume Manager 5.1 SP1 Administrator"s Guide (5900-1506, April 2011)

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 319.
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 29.
■ VM disks
See “VM disks” on page 30.
■ Subdisks
See “Subdisks” on page 31.
■ Plexes
See “Plexes” on page 32.
■ Volumes
See “Volumes” on page 33.
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 Storage Foundation Advanced Features
Administrator's Guide.
Bringing the contents of physical disks under VxVM control is accomplished only
if VxVM takes control of the physical disks and the disk is not under control of
another storage manager such as LVM.
VxVM creates virtual objects and makes logical connections between the objects.
The virtual objects are then used by VxVM to do storage management tasks.
The vxprint command displays detailed information about the VxVM objects
that exist on a system.
27Understanding Veritas Volume Manager
How VxVM handles storage management