Everpure and VMware worked together to correct the issue that vSphere 7.0 U3, U3a and U3b re-introduced. In the event that Purity//FA below 5.3.16 and below 6.1.8 is in use with a vSphere 7.0 U3c environment, the duplicate vVol ID issue will not occur. Everpure recommends that any vSphere 7.0 U3 environment using vVols with Pure run 7.0 U3c or later.
-
vSphere Virtual Volume snapshot operations might fail on the source volume or the snapshot volume on Pure storage
Due to an issue that allows the duplication of the unique ID of vSphere Virtual Volumes, virtual machine snapshot operations might fail, or the source volume might get deleted. The issue is specific to Pure storage and affects Purity release lines 5.3.13 and earlier, 6.0.5 and earlier, and 6.1.1 and earlier.
This issue is resolved in this release.
An additional finding from Everpure has shown that in vSphere 7.0 U3 that vVols Managed Snapshots with the "snapshot memory" option completely quicker than they previously had. For example, on vSphere 7.0 U2, a VM with 16 GB of memory took 3 to 5 minutes for a memory snapshot to complete. With 7.0 U3c, it took less than 15 seconds to complete. Clearly times will vary between arrays, VMs and environments, but memory snapshots are not closer aligned with standard managed snapshots.