Skip to content

vBlog.nl

All about technology

Menu
  • Home
  • VMware Cloud Director
  • vSphere
  • Automation
    • PowerCLI
    • PowerShell
    • Terraform
  • NSX
  • Horizon DaaS
  • About Us
Menu

VMware Virtual volumes or vVols

Posted on October 8, 2021

So today I will talk about VMware Virtual volumes or vVols. vVols are somewhat confusing sometimes so let’s dig in.

Table of Contents

  • What are VMware Virtual Volumes?
  • Why vVols?
  • vVols an inside look
    • vVol objects
    • Make up of a vVol
  • vVol benefits
    • Requirements to run vVols

What are VMware Virtual Volumes?


First of all a vVol is nothing like a a traditional VMware datastore (VMDK or NFS). vVols work completely different and are more of an “grouping” of Virtual machine files (disk, swap, etc.)

Secondly vVols are linked (or you could say mapped) directly to the underlaying storage array. These mapped objects on the storage array are called virtual volumes, hence the name vVols.

Another big difference to traditional datastores is that you do not have to create them upfront. They are automatically created when you deploy a VM, clone a VM, create a Snapshot, etc.

vVols are API driven. So the storage array must support this API driven deployment model leveraging the VMware API for Storage Awareness (VASA)

Why vVols?

So now that we know a bit more about vVols but why should you use them? Here are some reasons why to use vVols.

Automation
With vVols you have the ability to quickly provision VM workloads without the need to pick and choice the right storage type. You manage storage by using storage policies that you can assign and use for each VM using the vSphere Storage Policy management framework (SPBM).

Manageability
vVols offer you the option to more granularly manage your individual VM storage. You get the ability to monitor each VM individually. (setting up QoS, monitoring performance, capacity management, etc.)

Storage integration and offload capabilities
With vVols you can leverage the underlaying storage capabilities. For instance to offload snapshots to the storage Array instead of using vSphere based snapshots.

Overcoming traditional datastore shortcomings
Things like LUN count and path limits or creating NFS exports are a thing of the past.

vVols an inside look

vVol objects

Virtual machine files are stored directly on the storage array as virtual machine objects.

We can identify different types of objects:

  • Config – Configuration files, log files, lock files
  • Swap – Virtual machine memory swap
  • Data – Similar to a traditional VMDK

These files reside inside storage containers to form the vVols.

Make up of a vVol

vVol architecture components:

  • Storage Containers (SC)
  • Protocol Endpoints (PE)
  • API vendor integrations (VASA provider or VP)
  • vVols

Storage Containers:

Storage containers are a logical storage layer and are created by Storage Administrators. For each container you can define storage characteristics. Characteristics like capacity and restrictions (QoS for instance). These policy settings are set per VM instead of per datastore (the traditional way)

There is a direct relation between a Storage container and the storage array. If you create 2 storage containers on the storage array you will also have 2 vVols available on the ESXi host. Every storage array has at least 1 Storage Container.

Please note that a Storage Container is not a LUN !!

Protocol Endpoints:

Protocol endpoints are a proxy for IO between the vVol datastore and the ESXi host. In other words, they enable communication between the host and the array. PE’s support all standard protocols for example: iSCSI, NFS, FC and FCoE.

Protocol Endpoints are discoverable by ESXi host when performing rescan operations. PE’s are multi-path supported so multi-path policies can be used.

VASA provider:

The VASA provider, or VP, is a piece of software created by the storage vendor. The VP is used to expose the storage array capabilities to the ESXi hosts. In term the ESXi host can then use those capabilities to assign them to a Virtual Machine. The VP uses vSphere API’s and is usually incorporated on the storage controllers or supplies as a virtual appliance.

vVol benefits

Let’s have a look at some of the benefits of vVol’s shall we?

  • Policy based; you can easily assign another storage policy without impacting the VM’s
  • You can resized (grow and shrink). No need for UNMAP or other storage reclaim processes
  • No fixed sizes. You only use what is needed so each VM will consume the exact amount of storage needed.
  • Size is based on the array size and not the datastore size.
  • Dataservices are offloaded to the array (e.g. snapshots on array instead of VMware snapshots)
  • Simplified management for admins.

Requirements to run vVols

Lastly, lets quickly some up what is needed to use vVols

  • A storage array that supports vVols and can use VMware API’s for Storage awareness
  • vSphere vCenter and ESXi hosts
  • A vCenter standard and an ESXi Enterprise Plus license.

So there you have it, VMware Virtual volumes or vVols explained. I hope this information was useful and if you would like to know more about vVol’s have a look here.

If you liked this blog post please check out some of our other posts on vSphere here. Or for example some of our vCloud post here

Loading

Share on Social Media
twitter facebook linkedin reddit emailwhatsapptelegram

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent articles

  • vCloud Director API – Couldn’t connect to cloud server with the provided session id May 24, 2023
  • Horizon DaaS – Maximum sessions exceeded May 9, 2023
  • VMware Cloud on AWS with FSx for NetApp ONTAP December 28, 2022
  • Workspace ONE Access – Change certificate December 22, 2022
  • UI themes for VMware Cloud Director 10.4.1 and later December 16, 2022
  • VMware Tanzu Kubernetes Grid December 15, 2022
  • Workspace One Access – Not logged in to server FQDN. Please invoke Save before Sync December 12, 2022
  • NSX Edge configuration has failed. 1G hugepage support required. December 7, 2022
  • Horizon DaaS – Unable to connect to Desktop November 24, 2022
  • How to: Request and Install a Lets Encrypt Wildcard SSL on VMware Cloud Director 10.4 October 17, 2022

Tags

Automation bootstrapping Container Service Extension Credential Manager Desktone.log ESXi EUC EXi GPU Horizon DaaS Instant-Clone Logging NSX nsx-t PowerCLI PowerShell Putty Raspberry PI SSL Tanzu Terraform update vcd-cli vCenter vCloud vCloud Availability vCloud Director VDI vGPU VMware VMworld vSAN vSphere vVols workspace one Zerto

VMware Cloud Provider Blog

  • In the cloud world, one size doesn’t fit all
    by Vijoo Chacko on June 2, 2023 at 7:25 am

    The size make-up of enterprises in an industry can vary from sector to sector. Take for example, the commercial aviation industry. When did you last fly in a commercial plane that was not a Boeing or an Airbus? This is an industry clearly dominated by two major companies. Whereas the automotive industry is an example … Continued The post In the cloud world, one size doesn’t fit all appeared first on VMware Cloud Provider Blog.

  • Reminder: VMware Cloud Director Availability 4.2 and 4.3 End of General Support Approaching
    by Nikolay Patrikov on May 23, 2023 at 3:17 pm

    Keeping VMware Cloud Director Availability always up-to-date guarantees having all the latest and greatest features available for you and your tenants. But one more reason to consider it now is VMware Cloud Director Availability 4.2.x and 4.3.x will reach End of General Support (EOGS) on June 10, 2023, and will no longer be available for download from the VMware download pages. To ensure you … Continued The post Reminder: VMware Cloud Director Availability 4.2 and 4.3 End of General Support Approaching appeared first on VMware Cloud Provider Blog.

  • VMware Aria Rebranding on VMware Cloud Partner Navigator
    by Sulakshna Shrivastava on May 23, 2023 at 2:06 am

    We recently announced the renaming of the products within our Cloud Management family. These Aria rebranding updates have been implemented on the VMware Cloud Partner Navigator portal The post <strong>VMware Aria Rebranding on VMware Cloud Partner Navigator</strong> appeared first on VMware Cloud Provider Blog.

  • Upgrade vSphere now: vSphere 6.5 and 6.7 end of technical guidance is coming this November
    by Christopher Wong on May 20, 2023 at 3:00 pm

    With the general availability of VMware vSphere 8 Update 1, we would like to remind our Cloud Services Provider partner community that the end of general support for vSphere 6.5 and vSphere 6.7 was October 15, 2022. These versions are now under technical guidance until November 15, 2023. During the technical guidance phase, VMware does … Continued The post Upgrade vSphere now: vSphere 6.5 and 6.7 end of technical guidance is coming this November appeared first on VMware Cloud Provider Blog.

  • VMware NSX Migration for VMware Cloud Director 1.4.2 is now GA
    by Jaikishan Tayal on May 9, 2023 at 2:05 pm

    We’re thrilled to announce the release of the VMware NSX Migration tool for VMware Cloud Director 1.4.2! What is this Tool? If you are unaware of the VMware NSX Migration for VMware Cloud Director Tool, it can help you migrate your environment from NSX for vSphere to NSX T Data Center if you are currently … Continued The post VMware NSX Migration for VMware Cloud Director 1.4.2 is now GA appeared first on VMware Cloud Provider Blog.

©2023 vBlog.nl | Design: Newspaperly WordPress Theme