Skip to main content
Pure Technical Services

Virtual Volumes Quick Reference

Currently viewing public documentation. Please login to access the full scope of documentation.

KP_Ext_Announcement.png
vVols is an integration and management framework for external storage introduced with vSphere 6. vVols in Purity delivers many benefits for virtualized environments. Effortlessly streamline storage operations such as Pure's efficient snapshots and replication through Storage Policy Based Management at per-VM level granularity; automate compliance checking of assigned data services; rapid deleted volume recovery; and flexibility to move VMs and their data as needed.

vVols Best Practices Summary

Requirements

Recommendations

  • Purity//FA 6.1.8 or higher
  • FlashArray 400 Series, FlashArray//M, FlashArray//X, FlashArray//C
  • vCenter 6.5+ and ESXi 6.5+
    • vSphere 6.5 and 6.7 are end of life by VMware, 7.0 or higher should be used moving forward
  • Configure NTP for VMware environment and FlashArray
    • Ensure that all hosts, vCenter servers and arrays are all synced
  • Ensure that vCenter Server and ESXi Host managemen    t networks have TCP port 8084 access to FlashArray controller management ports.
  • Configure host and host groups with appropriate initiators on the FlashArray.
  • The 'pure-protocol-endpoint' must not be destroyed.
    • This namespace must exist for vVols management path to operate correctly.
  • Purity//FA 6.2.10 or later
  • vCenter 7.0 Update 3f (build 20051473) or later
  • ESXi 7.0 Update 3f (build 20036589) or later
  • When registering the VASA Provider, use a local FlashArray User
  • Do not run vCenter Servers on vVols
  • The Protocol Endpoint should be connected to Host Groups and not Individual Hosts.
  • Configure a syslog server for the vSphere environment
  • Configure snapshot policies for all Config vVols (VM home directories).
  • Use Virtual Machine hardware version 15 or later.
    • The Hardware Version will need to be 15 or later when the Virtual Machine needs to have more than 15 virtual devices per SCSI controller.

If using Virtual Volumes and FlashArray replication, ensure that anticipated recovery site is running vSphere 6.7 or later. 

As always, please ensure you follow standard Pure Storage best practices for vSphere.

Currently VMware does not support Stretched Storage with vVols. This means that due to limitations both with Purity//FA and vSphere, vVols is not supported with ActiveCluster. vVols are also not supported with ActiveDr.  

Pure Storage and VMware are actively partnered to develop support for stretched storage (ActiveCluster) for vVols and have targeted 1H of 2024CY for release, release timelines are subject to change. 

 

VMware has identified a critical issue when using vVols with ESXi 6.7 U2. Should vSphere Replication be in use with vVols hosts will PSOD. If using vSphere Replication in the ESXi environment using vVols, please run either ESXi 6.5 U3, 6.7 U1 or ESXi 6.7 U3. Refer to VMware's KB on the issue found here.


User Guides

Troubleshooting