- TMAN-19302: Recover from snapshot shows blank screen for NFS-backed VMs. Clarifying text has been added in this release. The functionality will be added in a future release of the vSphere plugin.
- TMAN-18080: Hardening VMFS VM restore when using inconsistent datastore mappings.
- TMAN-18446: VMFS PiT and environmental recovery would fail when CBT (changed block tracking) was enabled on the VM. This is a known VMware issue. In order to workaround this issue, the VMFS PiT recovery workflow will now present options for recovery when recovering a CBT enabled VM.
- TMAN-19213: Pod pgroup-auto protection group is always connected to the FlashArray volume when creating a datastore. To resolve this, the default protection group protection is not applied by default.
- TMAN-19214: Unable to move volume from a vgroup in a pod to a volume in the same pod outside of the vgroup. This has been fixed for arrays without SafeMode enabled but we are still evaluating how to best handle this on arrays with SafeMode enabled.
- TMAN-19215: When attempting to recover a VMFS-backed VM on an ESXi host that is not a member of a vSphere cluster, the error "A specified parameter was not correct: pool" was thrown and the workflow would not complete successfully. This has been fixed.
- TMAN-19216: vVol VM undelete with multiple storage containers was displaying incorrect information about the ability to recover a VM. This has been fixed.
- TMAN-19258: When attempting to use the vVol VM undelete workflows with VMs across multiple different storage containers, one of the vVol datastores will show all of the destroyed VMs as being able to recover from but the other vVol datastores will show none. This has been fixed.
- TMAN-19396: Resize and rename VMFS datastore fields are greyed out when no vgroups are present on a FlashArray. This has been fixed.