Vendors I plan to check out at #VMworld 2018

It’s here. VMworld 2018 is underway. I’ve just spent a great week in Nashville, a place I have wanted to visit for the longest time. Now it’s almost time to head to the airport and catch my flight to Las Vegas. As is usual at this time of year, there are a lot of announcements and briefing requests. In this post, I am going to share some of the announcements/briefings that I have been privy to, and share some of the things (mostly in the storage space) that I plan to learn more about over the next few days.

Changing policies on-the-fly with VVols

Last week, I was presenting at the VMware User Group (VMUG) event in Poland. My topic was SPBM, Storage Policy Based Management. This is the framework for consuming data services, whether these are provided from vSAN, Virtual Volumes or VAIO (IO Filters). You can get the presentation from here. One of the attendees who had implemented Virtual Volumes (aka VVols) asked a very interesting question about changing policies of a VVol based VM on-the-fly. The question is whether a policy change causes a new VVol has to be instantiated, data synced to original VVol and then the original VVol is…

Losing the VASA Provider and/or vCenter Server in VVols

With the release of vSphere 6.0 earlier this year, VMware introduced the eagerly anticipated VVols or Virtual Volumes. As we see more and more traction around VVols, a specific question has come up a number of times already. The question is basically: “What happens to VVols if I lose my VASA Provider or my vCenter Server, or indeed both of these components? Will I still have access to my devices?”.