Note VxVM uses the default naming conventions of vol # for volumes and vol for plexes in a volume.Įxample: Connections between VERITAS Volume Manager virtual objects and how they relate to physical disks. A volume consists of one or more plexes, each holding a copy of theselected data in the volume. For example, see the plex vol01-01.Ī volume is a virtual disk device that appears to applications, databases, and file systems like a physical disk device, but does not have the physical limitations of a physical disk device. A plex consists of one or more subdisks located on one or more physical disks. VxVM uses subdisks to build virtual objects called plexes. A VM disk can be divided into one or more subdisks.The default name for a VM disk is disk # (such as disk01) and the default name for a subdisk is disk.
VxVM allocates disk space using subdisks. The default disk group is rootdg (or root diskgroup),Ī subdisk is a set of contiguous disk blocks. Disk groups allow you to group disks into logical collections. A disk group configuration is a set of records with detailed information about related VxVM objects, their attributes, and their connections. Each VM disk has a unique disk media name (a virtual disk name).Ī disk group is a collection of VM disks that share a common configuration. A VM disk typically includes a public region (allocated storage) and a private region where VxVM internal configuration information is stored. Each VM disk corresponds to at least one physical disk or disk partition. A VM disk is under VxVM control and is usually in a disk group. When you place a physical disk under VxVM control, a VM disk is assigned to the physical disk. How VxVM Presents the Disks in a Disk Array as Volumes to the Operating System
#VERITAS VOLUME MANAGER 5 FREE#
It consists the remainder of the free space on the disk, that Volume Manager can use to assign a volume and is where application store the data. The default size of the private region is 2048. It stores information about disk headers, configuration copies, and kernel logs that Volume Manager uses to manage virtual objects. One partition contains the private region and the other contains the public region. Volume manager removes all of the partition table entries from the VTOC, and then rewrites the VTOC and creates two partitions on the physical disk. To bring a disk under Volume manager control means that Volume Manager creates virtual objects and establishes logical connections between those object and the underlying physical objects, or disk.
0 kommentar(er)
