0% found this document useful (0 votes)
219 views17 pages

Veritas Volume Manager Guide

The document discusses Veritas Volume Manager (VxVM) and its software architecture and components. It describes VxVM's virtual objects like VM disks, disk groups, subdisks, plexes and volumes. It also summarizes different recording methods like RAID 0 (striping), RAID 1 (mirroring), RAID 5 (striping with parity) and how they are implemented in VxVM. Hot relocation is also briefly mentioned.
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
219 views17 pages

Veritas Volume Manager Guide

The document discusses Veritas Volume Manager (VxVM) and its software architecture and components. It describes VxVM's virtual objects like VM disks, disk groups, subdisks, plexes and volumes. It also summarizes different recording methods like RAID 0 (striping), RAID 1 (mirroring), RAID 5 (striping with parity) and how they are implemented in VxVM. Hot relocation is also briefly mentioned.
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 17

Veritas Volume Manager Workshop

[email protected]

Vasily Pantyukhin

VM Vx shop rk Wo

Recording Methods

Software architecture
VxVM consists of a series of software layers that work together to create and manage volumes and the data that resides on them. It consists of utilities, a database to configure, monitor, and manage the system, and a volume driver. The principal component, the volume driver resides on top of the physical device drivers and below the file systems and other applications. It performs requested I/O and configuration changes. File systems and applications now access volumes instead of traditional UNIX physical disk partitions.

VM Vx shop rk Wo

VxVM Basics

Virtual objects and logical connections


VM Disks: When you place a physical disk under VxVM control, a VM disk is assigned to the physical disk. VM disk usually has two regions: private region -a small area where configuration information is stored. A disk header label, configuration records for VxVM objects (such as volumes, plexes and subdisks), and an intent log for the configuration database are stored here. The default private region size is 2048 blocks (1024 kilobytes), which is large enough to record the details of about 4000 VxVM objects in a disk group. public region -an area that covers the remainder of the disk and is used to store subdisks (and allocate storage space). basic disk types: sliced -the public and private regions are on different disk partitions. simple -the public and private regions are on the same disk area (with the public area following the private area). nopriv -there is no private region (only a public region for allocating subdisks).

VM Vx shop rk Wo

VxVM Basics

Virtual objects and logical connections


A Disk Group is a collection of VM disks that share a common configuration. A disk group configuration is a set of records with detailed information about related VxVM objects, their attributes, and their connections. The default disk group is rootdg (or root disk group). Subdisk is a set of contiguous disk blocks. A block is a unit of space on the disk. VxVM allocates disk space using subdisks.

VM Vx shop rk Wo

VxVM Basics

Virtual objects and logical connections


Plex consists of one or more subdisks located on one or more physical disks. You can organize data on subdisks to form a plex by using the following methods: - concatenation - striping (RAID-0) - mirroring (RAID-1) - striping with parity (RAID-5)
Volume vol01 contains one plex named vol01-01. The plex contains one subdisk named disk01-01. The subdisk disk01-01 is allocated from VM disk disk01

Volume consists of one or more plexes. All subdisks within a volume must belong to the same disk group.
Volume vol06 contains two plexes named vol06-01 and vol06-02 Each plex contains one subdisk Each subdisk is allocated from a different VM disk (disk01 and disk02)

VM Vx shop rk Wo

VxVM Basics

Virtual objects and logical connections

VM Vx shop rk Wo

Recording Methods

RAID 0Concatenation

VM Vx shop rk Wo

Recording Methods

RAID 0Striping

Each disk in a stripe is generally assumed to be on its own independent data channel, allowing the transfer rate of a RAID 0 implementation to approach the sum of the transfer rates of each of the drives.

VM Vx shop rk Wo

Recording Methods

RAID 0Striping

VM Vx shop rk Wo

Recording Methods

RAID 0Striping

VM Vx shop rk Wo

Recording Methods

RAID 1Mirroring

Designed to optimize data availability rather than speed, RAID 1 duplicates each write transaction to one or more mirror disks. Mirrored systems can be used to improve the IOPS performance of read operations, because the least busy drive can be selected to service requests. Because both drives must be involved in write operations, write performance may be slightly lower than that of an independent drive.

VM Vx shop rk Wo

Recording Methods

RAID 0+1Striping + Mirroring

RAID 0+1 systems can tolerate the failure of a disk, and continue to deliver data with virtually no performance degradation, unlike RAID 5. However, RAID 0+1 systems carry the higher cost of mirrored systems, as data requiring protection needs twice the disk space of simple independent spindles.

VM Vx shop rk Wo

Recording Methods

RAID 1+0Mirroring + Striping

RAID 1+0 systems can tolerate the failure of one or more disks, and continue to deliver data with virtually no performance degradation, unlike RAID 5. However, RAID 1+0 systems carry the higher cost of mirrored systems, as data requiring protection needs twice the disk space of simple independent spindles.

VM Vx shop rk Wo

Recording Methods

RAID 5Striping + Distributed Parity

If the data is distributed across the group of drives in blocks equal in size or larger than most I/O requests, the drives can respond independently to requests, and even to multiple requests simultaneously. This has the effect of allowing RAID 5 to have very good random read performance. Conversely, if the block sizes in a stripe are smaller than the average size of an I/O request, forcing multiple drives to work together, RAID 5 systems can also enjoy good sequential performance.

VM Vx shop rk Wo

Recording Methods

RAID 5Striping + Distributed Parity

VxVM allows each column of a RAID-5 plex to consist of a different number of subdisks. The subdisks in a given column can be derived from different physical disks. Additional subdisks can be added to the columns as necessary. Striping is implemented by applying the first stripe across each subdisk at the top of each column, then applying another stripe below that, and so on for the length of the columns. Equal-sized stripe units are used for each column. For RAID-5, the default stripe unit size is 16 kilobytes.

VM Vx shop rk Wo

Recording Methods

Hot Relocation

Thank You

You might also like