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.
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.
Internal Information
-
Troubleshooting KBs: Troubleshooting Flowchart/Workflow
-
Support vVol FAQ: Virtual Volumes (vVols) FAQ
-
Have questions? Ask the experts in the Everpure Slack channel #ask-vvols
User Guides
- vVols User Guide: Storage Policy Based Management
- vVols User Guide: vVol Datastore
- Web Guide: Virtual Volumes Quick Start Guide
- Web Guide: Implementing vSphere Virtual Volumes with FlashArray
- vVols User Guide: The FlashArray VASA Provider
- vVols User Guide: Types of vVols
- vVols User Guide: Replicating vVols
- vVols User Guide: Configuring Host Connectivity
- vVols User Guide: NVMe-oF vVols
- Web Guide: Managing the VASA Certificates with purecert via the CLI
- vVols User Guide: Best Practice Summary
- vVols Deep Dive: Understanding Virtual Volumes and Failure Scenarios
- vVols User Guide: Protocol Endpoints
- vVols Deep Dive: Array Based Replication with vVols
- vVols User Guide: Migrating VMs to vVols
- vVols User Guide: Snapshots of vVols
- Using VMware Site Recovery Manager with the Everpure FlashArray
- Web Guide: Configuring Multiple Non-Linked vCenters with the FlashArray VASA Provider
- vVols Deep Dive: What Happens when a Single VASA Service is Unreachable?
- vVols User Guide: vVol Binding
- vVols User Guide: vVols Reporting
- vVols User Guide: Terminology
- vVols User Guide: Introduction to vVols
- vVols Deep Dive: Lifecycle of a VASA Operation
Release Notes
- VASA and vVols Related Fixes by ESXi Release
- FlashArray VASA Provider Version by Purity Release
- Purity//FA 5.3.x Release Notes
- What's New with VASA Provider Version 2.0.0?
- What's new with VASA Version 1.2.0?
- What to expect when upgrading to Purity 5.3 when using vVols
- What's new with VASA Version 1.1.0?
How-To's
- Web Guide: Managing the VASA Certificates with purecert via the CLI
- How To: Renewing the Storage Provider Certificate that is Expired or Going to Expire
- How To: Change the IP Address of a FlashArray Controller when using vVols on the FlashArray
- Web Guide: Configuring Multiple Non-Linked vCenters with the FlashArray VASA Provider
- How To: Managing vVol Storage Provider Certificates during a FlashArray Hardware NDU or Controller Replacement
- Virtual Volume How To's
- Web Guide: vSphere Virtual Volume VM Recovery and Snapshot Workflows
Videos
Troubleshooting
- Virtual Volumes (vVols) FAQ
- Troubleshooting: vCenter Storage Provider Errors and Host Protocol Endpoint Connection Errors
- A 25 second pause in I/O during a single link loss with iSCSI
- How To: Renewing the Storage Provider Certificate that is Expired or Going to Expire
- Troubleshooting: VASA Operations Fail with Vendor Specific Error - Duplicate Key Found
- Troubleshooting: CBT Enabled vVols VMs Fail QueryChangedDiskAreas when FlashArray SafeMode is Enabled
- Troubleshooting: After upgrading to Purity//FA 6.0 or 6.1 SRM is reporting vVol VMs are not replicated and queryReplicationGroup fails
- Troubleshooting: Storage Providers are offline after a Purity upgrade to 5.1.6+
- Troubleshooting: vVols Mental Model
- Troubleshooting: PowerShell "Object Reference Not Set" Failure with PowerCLI 12
- Troubleshooting: Deploying a vVol VM fails to create a FlashArray Volume Group on ESXi 6.7 U1
- vVols log(s) Troubleshooting and Analysis
- Storage vMotion using VVOL datastore on Pure array results in Error 195887107
- Troubleshooting: vVols report "LOGICAL BLOCK ADDRESS OUT OF RANGE" SCSI errors
- Troubleshooting when vVol Datastore Fails to Mount on UCS Server