Editor’s Note: VMware vVols End-of-life Update (2025)
VMware has announced the deprecation and end-of-life (EOL) of vSphere Virtual Volumes (vVols):
- vVols remain supported only through VMware vSphere 8.0 and VMware Cloud Foundation (VCF) 9.0. Support for these versions will end between 2027-2028.
- No new feature development for vVols is planned; only limited support is available from VMware until EOL.
- Official retirement will occur with VCF 9.1 (expected 2028); vVols will not be supported in any new VMware releases after that point.
If you are currently using vVols:
Pure Storage recommends that you begin planning your migration to supported VMware storage solutions (such as VMFS or NFS) well before EOL. For current integration and migration resources, up-to-date documentation, or personalized help, please visit our technical support portal or contact your Pure Storage representative.This blog post is for historical and archival purposes only. Do not use as guidance for new deployments. For current storage integration options and migration toolkits, refer to our latest migration guides and platform resources.
Since joining Pure Storage® in February 2015, I’ve had the opportunity to be involved in the development and release of several features and Purity updates. Purity//FA 5.0.0 was one of the first releases where I was more involved with the alpha, beta, and release candidate testing/validation. The 5.0.0 release was a milestone release, as two big features were released. ActiveCluster™ (active-active stretched storage support) and vSphere Virtual Volumes(vVols) were both GA in 5.0.0. However, at the time, they were not supported together, meaning that you couldn’t stretch your vVols environment.
There are a few reasons why Pure wasn’t able to support stretched vVols at that time and why Pure has not released support for stretched vVols up to this point:
- The concept of stretched vVols was not part of the vVols specification.
- vSphere High Availability (HA) and VM Component Protection (VMCP) had a lack of support or missing support for vVols.
- Pure needed additional vVols API support for a more complete integration and support with ActiveCluster and vVols.
- Both Pure and VMware needed to make core improvements to the performance, reliability, availability, and scale of vVols.
Because supporting stretched vVols is so crucial, VMware engineering had to be involved. Over the course of the past few years, VMware and Pure have been working together toward improving the overall health and performance of vVols. There are many notable fruits of this labor! In Purity//FA 6.2, the updated VASA Provider 2.0 was released and object limits were further increased. In vSphere 7.0, there have been improvements to specific operations, batching, and overall stability. With vSphere 8.0, there will be additional improvements to these aspects as well.
With all of this groundwork being laid, both VMware and Pure have been focused on getting support for active-active stretched storage and vVols. In fact, there’s a target release date for support for vVols and active-active stretched storage for 2H CY2023. Between now and the release, both VMware and Pure will be actively working together as design partners. The specification changes are being finalized now, and from there, it will move to the development stage and then into testing and validation.
Why does this matter so much? Because it matters to customers. In many of my previous conversations about vVols with prospective and current customers in the EMEA market, they asked “Can it be protected with ActiveCluster?” or “Can we stretch vVols and will it be active-active?” Bottom line, ActiveCluster wasn’t just a feature for prospective customers or customers in EMEA. ActiveCluster was a business requirement to even get a foot in the door. As such, we haven’t seen as high of an adoption rate of vVols in the EMEA market. Since vVols didn’t have ActiveCluster support, the option to deploy it or use it just wasn’t there for so many users.
