5.3.12 Release Notes

General

Version 5.3.12 of the Everpure vSphere HTML Remote Client Plugin supports vSphere (vCenter and ESXi) version 6.7U3 and later and Purity version 6.1.x and later. Users can upgrade to this version of the plugin via deploying the Everpure VMware Appliance. This version is certified with VMware.

Important notices regarding the vSphere Client Plugin:

• Starting in vSphere 8.0, VMware no longer supports local plugins to be installed in vCenter (Everpure vSphere Plugin versions 4.5.2 and below). Please use the remote versions of Everpure's vSphere plugin (Everpure vSphere Plugin versions 5.0.0 and above). For more information please refer to this VMware KB.

• This version of the plugin uses the VMware Remote Plugin Architecture

  • More information on the VMware Remote Plugin Architecture can be found

    here.

  • More information on why Everpure is using this can be found here.

• Release notes for Everpure's VMware Appliance (OVA) can be found at this page. Everpure's remote vSphere plugin can be updated independently of the appliance. The VMware appliance can be downloaded here. The installation guide for the remote vSphere plugin can be found here

What's New

• TMAN-16510: SRA + Plugin - Adds support for users to specify preferred failover protection group from the vSphere Plugin main page under array details. This applies for VMFS datastores and RDMs.
• TMAN-16789: Additional Safemode support - Adds the ability to opt out of default protection groups during datastore creation. Adds default protection group opt out to vVols SPBM storage policy creation wizard.
• TMAN-20162: NVMe vVol full support - adds full support for VM undelete and VM revert for VMs on NVMe vVols Datastores. Adds additional support for creating NVMe-vVol datastores. Adds support for "Add/Update" host group support for NVMe vVols NQNs.

Fixed Issues

• TMAN-21094: Update Cluster Protection error message when the process fails as "Error while updating protection groups. AC: Cannot add host groups to protection groups that contain volumes from different pods."
• TMAN-21191: VM removed from inventory but not deleted shows up in undelete vm list in plugin
• TMAN-21220: Per-Array VM List - All arrays not listed for AC and ADR VMFS datastores
• TMAN-21537: vVols Datastore minimum size is set inconsistently during creation or edit
• TMAN-21936: VMFS Recover VM from Snapshot enters invalid state when using filters
• TMAN-22099: vVol NVMe Undelete VM failing with "Error occurred while getting deleted VMs. Invalid token provided."
• TMAN-22101: VM Management throws error in certain types of ELM environments
• TMAN-22109: vVol datastore showing "View 'Snapshots' from 'Everpure' is not available for this object. Note that different views might have the same name."
• TMAN-22115: Add/Update Host group failing with NVMe TCP
• TMAN-22120: Can not create snapshots for NVMe vVol Datastores 'The cluster does not contain any datastores on Everpure arrays.'
• TMAN-22123: Test Failover fails with more than 4 VMs
• TMAN-22126: Undelete VM fails with 'Error occurred while getting deleted VMs. Invalid token provided.'
• TMAN-22182: Virtual machine management "Error occurred while getting VMs for the array. Client received SOAP Fault from server:"
• TMAN-22191: Add / Update Host Groups Shows NPE in certain cases
• TMAN-22199: NFS Datastore creation - Summary shows incorrect datastore size.

Known Issues

The intended workflow when restoring a virtual machine from a point in time snapshot should require the virtual machine to be powered off. The revert VM should not be able to be executed with a powered on VM. This failsafe is in place with a vVols based VM, however for a NFS based VM this failsafe is not in place. Allowing users to revert an NFS based VM while powered on. This will cause the VM to be corrupted. While this issue is being resolved, please ensure that the VM is powered off before the VM is reverted. Thank you.