vVols is an integration and management framework for external storage introduced with vSphere 6.5. vVols in Purity 5.x 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.
- Purity 5.1.15+
- Purity 5.3.6+ is required for SRM + vVols support
- FlashArray 400 Series, FlashArray//M, FlashArray//X, FlashArray//C
- vCenter 6.5+ and ESXi 6.5+
- Configure NTP and Syslog for VMware environment and FlashArray
- Ensure that vCenter Server and ESXi Host management 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 5.3.10 or later
- vCenter 6.7 U3 or later
- ESXi 6.7 U3 P03 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 snapshot policies for all config vVols (VM home directories)
- Use Virtual Machine hardware version 11 or later.
If using Virtual Volumes and FlashArray replication, ensure that anticipated recovery site is running vSphere 6.5 or later.
If using vVols array based replication for failover and recovery methods, Pure Storage strongly recommends running Purity 5.3.6 or later.
As always, please ensure you follow standard Pure Storage best practices for vSphere.
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.