Duplicate vVol IDs observed When vSphere 7.0 Update 3 is used in conjunction with Pure Storage array

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:

After upgrading to VMware ESXi 7.0.3 build-18644231 or higher a duplicate vVols ID is seen on new snapshots.

Environment

VMware vSphere 7.0.x.

Cause

VMware is currently investigating this issue in-conjunction with Pure Storage which impacts a subset of arrays when the vSphere environment is upgraded to 7.0 update 3.
There is a critical issue that was 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.

Resolution

This is an active investigation, Please subscribe to this KB for updates

Workaround:
Purity//FA should be upgraded to 5.3.16+ or 6.1.8+ before upgrading to vSphere 7.0 U3 or higher. Prior to upgrading the vSphere environment to 7.0 U3 or higher, please work with Pure Storage support to confirm that all FlashArrays using vVols are upgraded to Purity//FA 5.3.16+ or 6.1.8+