Purity//FA should be upgraded to 5.3.16+ or 6.1.8+ before upgrading to vSphere 7.0 U3 or higher. There is a critical issue that was re-introduced with the release of vSphere 7.0 U3 and U3a that will cause duplicate vVol IDs when vSphere takes managed snapshots of vVols based VMs on the FlashArray. Prior to upgrading the vSphere environment to 7.0 U3 or higher, please work with Everpure support to confirm that all FlashArrays using vVols are upgraded to Purity//FA 5.3.16+ or 6.1.8+
New Feature
-
vVols Managed Snapshots can now Batched Prior to vSphere 7.0 U3 when vSphere issued snapshotVirtualVolume requests to a VASA provider on a single virtual disk was provided per request. With the release of vSphere 7.0 U3 VMware has enhanced the snapshotVirtualVolume request to provide multiple virtual disks in one request. This will help decrease the stun time during managed snapshot creation.
Known Issue with vSphere 7.0 U3
-
Virtual machine snapshot operations fail in vSphere Virtual Volumes datastores on Purity version 5.3.12 or lower
Virtual machine snapshot operations fail in vSphere Virtual Volumes datastores on Purity version 5.3.12 with an error such as
An error occurred while saving the snapshot: The VVol target encountered a vendor specific error.The issue is specific for Purity versions lower that 5.3.13.