![]() ![]() Other – vSphere solution specific object.Config – VM Home, Configuration files, logs.There are five different types of vVols, and each of them maps to a different and specific virtual machine file. vVols are stored in storage containers and mapped to virtual machine files/objects such as VM swap, VMDKs, and their derivatives. VVols are a new type of virtual machine objects, which are created and stored natively on the storage array. ![]() The following is a summarized description and definition of the key components of vVols: This document provides a summarized description and definitions of the key components of Virtual Volumes. It is important to familiarize yourself with the concepts that are relevant to vVols and their functionality. ![]() This mapping allows vSphere to offload intensive storage operations such as snapshots, cloning, and replication to the storage system. vVols map virtual disks and their respective components directly to objects, called vVols, on a storage system. Rather than arranging storage around features of a storage system, vVols arranges storage around the needs of individual virtual machines, making storage virtual machine-centric. The vVols functionalities allow for the differentiation of virtual machine services on a per-application level by offering a new approach to storage management. With the traditional approach, differentiation on a per virtual machine level is difficult. However, a single Virtual Datastore contains multiple virtual machines, which might have different requirements. Typically, the Virtual Datastore is the lowest granular level at which data management occurs from a storage perspective. The storage array responds with an individual storage container that precisely maps to application requirements and boundaries. vSphere administrators use policies to communicate application requirements to the storage array. With vVols, this approach is fundamentally changed. Storage administrators had to forecast well in advance what storage services might be needed in the future, usually resulting in the overprovisioning of resources. vSphere administrators could not easily specify specific requirements on a per-VM basis.Ĭhanging service levels for a given application usually meant relocating the application to a different storage pool. Since a single, homogeneous storage pool would potentially contain many different applications and virtual machines this approach resulted in needless complexity and inefficiency. A storage administrator would configure array resources to present large, homogenous storage pools that would then be consumed by vSphere administrator. Historically, vSphere storage management has been based on constructs defined by the storage array: LUNs and filesystems. Virtual Datastores are purely logical constructs that can be configured on the fly, when needed, without disruption, and don’t require formatting with a file system.The Virtual Datastore defines capacity boundaries, access logic, and exposes a set of data services accessible to the virtual machines provisioned in the pool. The precise consumption of storage resources eliminates overprovisioning. vVols improve resource utilization by enabling more flexible consumption of storage resources, when needed and with greater granularity.vVols simplifies the delivery of storage service levels to applications by providing administrators with a finer control of storage resources and data services at the VM level that can be dynamically adjusted in real-time.By using policy-driven automation as the operations model, provisioning and change management are simplified and expeditated. vVols simplifies storage operations by automating manual tasks and reducing operational dependencies between the vSphere Admin and the Storage Admin.Some of the primary benefits delivered by vVols are focused on operational efficiencies and flexible consumption models. VVols enables application-specific requirements to drive storage provisioning decisions while leveraging the rich set of capabilities provided by existing storage arrays. VSphere Virtual Volumes or vVols implements the core tenets of the VMware Software-Defined Storage vision to enable a fundamentally more efficient operational model for external storage in virtualized environments, centering it on the application instead of the physical infrastructure. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |