{"id":4620,"date":"2024-04-16T20:54:52","date_gmt":"2024-04-17T01:54:52","guid":{"rendered":"https:\/\/www.jasemccarty.com\/blog\/?p=4620"},"modified":"2024-05-29T12:54:29","modified_gmt":"2024-05-29T17:54:29","slug":"are-vvols-easy-out","status":"publish","type":"post","link":"https:\/\/www.jasemccarty.com\/blog\/are-vvols-easy-out\/","title":{"rendered":"Are vVols an Easy Way off of vSphere?"},"content":{"rendered":"

\"\"<\/a>I remember when \u00a0vVols were introduced over a decade ago. To me, the promise of getting all the array side benefits of native volumes with the flexibility of traditional vSphere\u00a0provisioning and management was a very revolutionary approach.<\/p>\n

Anyone who is familiar with the history of vVols knows that they did a have a rocky start, especially since they were introduced in a similar timeframe as vSAN.<\/p>\n

Having worked at VMware during that time, I did see the adoption of vVols rise, especially once storage vendors decided to embrace them and VMware decided to develop replication and SRM support.<\/p>\n

With the current climate around the changes since VMware was purchased, I started thinking about it…<\/p>\n

For the VMware customers who have decided to implement vVols, the technology might be somewhat of an easy button to move data from vSphere to an alternate hypervisor (or even back to bare metal).<\/p>\n

I say this, because the idea of vVols is to present array volumes, with some metadata\/mapping to vSphere through the VASA service.<\/p>\n

Ultimately a vVol volume is a volume that contains the native file system of the virtual machine it is being presented to.<\/p>\n

So\u2026 A vVol volume could be copied to another volume and that volume could be presented as a passthrough disk to an alternate hypervisor or bare metal server.<\/p>\n

I tried this out recently with a Windows system with the \u00a0Hyper-V role and the migration was pretty painless. The HyperV VM had a passthrough disk, but Hyper-V also has a native workflow to convert a passthrough disk to a .vhdx.<\/p>\n

And yes, this requires some downtime, but what’s the downtime cost vs other costs?
\n<\/p>\n

The process<\/h2>\n
    \n
  1. The VMware VM needs to be deployed to a vVol datastore.<\/li>\n
  2. Determine the volume(s) you want to make copies of to present to your alternate hypervisor.<\/li>\n
  3. The volumes could be snapped (VM off or running with “crash consistency”)<\/li>\n
  4. Present those volumes to your alternate Hypervisor host (as you would an RDM to one or more vSphere hosts)<\/li>\n
  5. Create a VM on the alternate hypervisor’s platform and attach the volume as you would a passthrough disk.<\/li>\n
  6. Ensure the VM’s configuration (cpu, ram, networking) matches the original VMware VM’s configuration.<\/li>\n
  7. Power on the VM.<\/li>\n<\/ol>\n

    My experience<\/h2>\n

    Step 1 & 2.<\/strong> I took a VM on a vVol datastore and determined the volume (C: drive here) I needed a copy of<\/p>\n

    \"\"<\/a><\/p>\n

    On my system, the C: drive of my Windows VM is a volume named Data-b4d8d085 in the vvol-WINDOWS-4ed98cd0-vg volume group on my array. *Different platforms will have different methods to see this<\/em><\/p>\n

    Step 3.<\/strong> Took a snapshot of the volume (C: drive here)<\/p>\n

    \"\"<\/a><\/p>\n

    Using the vSphere tools I have for my platform, I created a snapshot of the C: drive volume. *Different platforms will have different methods for this<\/em><\/p>\n

    Step 4.<\/strong> Copied that snapshot to a new volume<\/p>\n

    \"\"<\/a><\/p>\n

    *Different platforms will have different methods for this<\/em><\/p>\n

    Step 5.<\/strong> Attached that new volume to my Hyper-V host<\/p>\n

    \"\"<\/a>*Different platforms will have different methods for this<\/em><\/p>\n

    My Hyper-V host was already configured to use iSCSI to connect to my array, and it automatically showed up upon being presented.<\/p>\n

    \"\"<\/a><\/p>\n

    Step 6.<\/strong> Created a VM on my host with the Hyper-V role<\/p>\n\n\n\n\n
    \"\"<\/a>
    \nName and Location<\/td>\n    		\"\"<\/a>
    \nGeneration 2 for SCSI disks<\/td>\n<\/tr>\n
    \"\"<\/a>
    \nDon’t add a disk<\/td>\n    		\"\"<\/a>
    \nFinish<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Notice that I did not add a hard disk yet. I’ll add the local volume as a passthrough disk in the next step.<\/p>\n

    Step 7. Modified the VM’s configuration<\/p>\n\n\n\n
    \"\"<\/a>Select the Passthrough Disk<\/td>\n\"\"<\/a>Disable Checkpoints<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Step 8.<\/strong> Powered on the VM.<\/p>\n

    \"\"<\/a><\/p>\n

    Some things to consider<\/h2>\n
      \n
    • VMware tools are very hard to remove once a Windows VM has been brought into Hyper-V.
      \nThere are a few mechanisms to remove them afterwards, but removing them before the migration is easiest.<\/li>\n
    • The Hyper-V VM is using a passthrough disk. If passthrough disks aren’t desired, you’ll need to determine what the migration process is in your alternate hypervisor. Fortunately Hyper-V makes it easy to migrate a passthrough disk to a vhdx<\/span>, albeit offline.<\/li>\n<\/ul>\n

       <\/p>\n

      Summary<\/h2>\n

      This manual process shows that a VMware vSphere VM residing on vVols can be easily migrated to an alternate platform. With a little elbow grease and some time, this could be scripted if the platforms you’re using support automation tools like PowerShell or others.<\/p>\n

       <\/p>\n","protected":false},"excerpt":{"rendered":"

      I remember when \u00a0vVols were introduced over a decade ago. To me, the promise of getting all the array side benefits of native volumes with … <\/p>\n","protected":false},"author":1,"featured_media":4656,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[211,10,12,168,13],"tags":[],"class_list":["post-4620","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-microsoft","category-storage-2","category-virtualization","category-vsan","category-windows"],"_links":{"self":[{"href":"https:\/\/www.jasemccarty.com\/blog\/wp-json\/wp\/v2\/posts\/4620","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.jasemccarty.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.jasemccarty.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.jasemccarty.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.jasemccarty.com\/blog\/wp-json\/wp\/v2\/comments?post=4620"}],"version-history":[{"count":15,"href":"https:\/\/www.jasemccarty.com\/blog\/wp-json\/wp\/v2\/posts\/4620\/revisions"}],"predecessor-version":[{"id":4648,"href":"https:\/\/www.jasemccarty.com\/blog\/wp-json\/wp\/v2\/posts\/4620\/revisions\/4648"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.jasemccarty.com\/blog\/wp-json\/wp\/v2\/media\/4656"}],"wp:attachment":[{"href":"https:\/\/www.jasemccarty.com\/blog\/wp-json\/wp\/v2\/media?parent=4620"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.jasemccarty.com\/blog\/wp-json\/wp\/v2\/categories?post=4620"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.jasemccarty.com\/blog\/wp-json\/wp\/v2\/tags?post=4620"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}