Virtual Volumes ( #VVols) are a new #VMware object type that corresponds to a Virtual Machine (VM) disk, and its snapshots and fast-clones. There are different types of VVol objects, including Config-VVol, Data-VVol (equivalent to VMDK), Memory-VVol, and Swap-VVol. On the storage system, VVols reside in VVol datastores, also known as storage containers. VVol datastores are a new type of VMware datastore, in addition to VMFS and NFS datastores, which allow VVols to map directly to a storage system. Whereas VMware VMFS and NFS datastores are managed and provisioned at the LUN or file system-level, VVol datastores are more granular: VMs or virtual disks can be managed independently. You can create VVol datastores based on one or more underlying storage pools and then allocate a specific portion of the pool to be used for the VVol datastore and its associated VVols. VMware vSphere 6.0 and later uses Storage Policy-Based Management (SPBM) to define application or VM-specific storage requirements. These storage policies dictate which storage containers are compatible with VVols. A capability profile, configured by the storage administrator, is a set of performance characteristics for a VVol datastore on the storage system. These characteristics are based on the underlying storage pools and include three categories of capabilities: Service level-based provisioning Usage tags Storage properties
https://www.emc.com/en-gb/documentation/unity-family/unity-p-vvols-config/01-vxe-tn-vvols-br-manage-vvol-datastores.htm
No comments:
Post a Comment