26Understanding Veritas Volume Manager

How VxVM handles storage management

See Disk device naming in VxVM” on page 78 and Changing the disk-naming scheme” on page 91 for details of the standard and the enclosure-based naming schemes, and how to switch between them.

Virtual objectsVirtual objects in VxVM include the following:Disk groupsVM disksSubdisksPlexesVolumes

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.

Note: 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

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.

VxVM creates virtual objects and makes logical connections between the objects. The virtual objects are then used by VxVM to do storage management tasks.

Note: The vxprint command displays detailed information on existing VxVM objects. For additional information on the vxprint command, see Displaying volume information” on page 264 and the vxprint(1M) manual page.

Combining virtual objects in VxVM

VxVM virtual objects are combined to build volumes. The virtual objects contained in volumes are VM disks, disk groups, subdisks, and plexes. Veritas Volume Manager objects are organized as follows:

VM disks are grouped into disk groups