5.3.4 Release Notes

General

Version 5.3.4 of the Everpure vSphere HTML 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 by VMware.

What’s New

• 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 Why Everpure is Deprecating the Local vSphere Plugin in Favor of the Remote vSphere Plugin.
• Release notes for Everpure's VMware Appliance (OVA) can be found at Everpure VMware Appliance Release Notes. Everpure's remote vSphere plugin can be updated independently of the appliance. The VMware appliance can be Everpure VMware Appliance Quick Reference .
  • When the OVA's operating system needs to be updated, the OVA will need to be upgraded first in order to see the remote vSphere plugin upgrade options. When running puresw list if your target version vSphere plugin version is not visible but the OVA says it can be upgraded, upgrade the OVA first.
• NFS 4.1 support
  • The plugin now allows the provisioning of datastores with NFS 4.1 protocol. This requires Purity 6.4.10 or later on the hosting FlashArray.
• NFS VM Undelete
  • Allows the restoring of a virtual machine from pre-created snapshots for VMs that no longer exist in VMware.
• NFS VM Point in Time Recovery
  • Enables greatly simplified recovery of NFS-backed VMs using FlashArray snapshots

Fixed issues

• TMAN-19381: There were extra networks being created by the vSphere plugin on Everpure's VMware appliance and the vSphere plugin wouldn't always use the user defined IP ranges. This has been fixed.

Known issues

• If an array's management ports were accessible upon adding the array to the vSphere plugin and later became inaccessible, loading certain windows in the vSphere plugin might take greater than 10 minutes. To workaround this issue there are currently two options:
  1. Wait until the array list populates in the vSphere plugin screen and remove the inaccessible array
  2. If the vSphere environment has only had Pure's remote plugin installed, un-registering the plugin and registering it again should clear out the array connections that existed and the existing accessible arrays can be added back
  • Pure is currently evaluating options to improve this situation in TMAN-19146