Release: September 2020
General
Version 4.4.0 of the Everpure vSphere HTML Client Plugin supports vSphere (vCenter and ESXi) version 6.5 and later and Purity version 4.10 and later.
Users can upgrade to this version of the plugin from previous release version 4.x or higher. This version is certified by VMware.
What’s New
- Support for ActiveDR
- Provisioning datastores or copies
- Backend insights of datastore (show lag time, direction etc)
- Tolerance of volumes being in an ActiveDR pair
- Create snapshot of a single vVol VMDK
- Set the ESXi host personality when creating new hosts in a new host group.
Fixed issues
- Wrong status on verifying protocol-endpoint in creating vVol datastore. PE should show as not found when it has not been created yet.
- Unable to Filter by VM Name in vSphere plugin. Filtering did not work when the VM was in a sub-folder.
- Problems retrieving pods from other flasharrays in create datastore wizard if one array is offline or has api-token issue. If one array connection had an issue, the plugin would not find any pods on any healthy array.
- Error loading array list. Seemingly arbitrary error when trying to perform plugin operations in linked mode. The underlying issue was that different vCenters would not coordinate responses and sometimes queries went to the wrong vCenter. The plugin now checks for the correct vCenter connection.
- Create vVol snapshot button was missing. This was remove somewhat on purpose due to an old issue, that issue has been fully resolved and this feature has been returned.
- Datastore type not disabled when user selects copy from VMFS snapshot. This allows the choice of vVols for a VMFS copy which is invalid, it no longer shows this option.
- Error when resizing a datastore: Invalid Size, Size Must be a multiple of 512. This was a regression and has been fixed.
- Snapshot info missing when creating VMFS datastore from snapshot. Old plugin showed the snapshot information during the wizard, this has been added back.
- Deletion of datastore requires manual rescan when host in maintenance mode. Maintenance mode hosts were skipped when removing datastores, they are now cleaned up.
- Unable to create datastore in maintenance mode. If the chosen host was in maintenance mode, the creation would fail. This is now supported.
Known issues
- Plugin does not offer custom per-feature permissions. Details here.