Everpure Cloud Dedicated Release Notes v6.10.3

Overview

Infrastructure Encryption (IE) for Azure Storage Account

New Everpure Cloud Dedicated version 6.10.3 deployments on Azure will leverage Infrastructure Encryption for the Storage Accounts. With this feature, 256-bit AES encryption is used at the Azure Storage infrastructure level for double encryption, providing an additional level of security. This feature is automatically enabled for new deployments of Everpure Cloud Dedicated 6.10.3 on Azure.

Resiliency Tunables for Everpure Cloud Dedicated on Azure

During Azure maintenance or brief infrastructure events, the array can experience short-lived increases in I/O latency to backend managed disks. These spikes may be transient yet noticeable by hosts and applications.

To harden array behavior against these conditions, Everpure Cloud Dedicated 6.10.3 on Azure comes with a newly configured set of array-level tunables. These adjust how controllers interpret delayed I/O, coordinate takeovers, and manage internal leases so the array prefers riding out transient backend conditions rather than initiating a controller failover.

For more information, please refer to the following article - Everpure Cloud Dedicated Resiliency Tunables.

Bug Fixes

Everpure Cloud Dedicated v6.10.3 on Azure fixed an issue where cache drive latency spikes could allow >256 inflight cache operations, causing IO threads to busy-wait and potentially trigger controller failover. The cache device queue depth is now restricted to prevent overload.

The NVMe health‑check timeout for Everpure Cloud Dedicated on Azure is now configurable instead of using a hard‑coded 2‑second limit. This allows better tolerance of short Azure infrastructure pauses without compromising detection of genuine hangs.

Other Purity improvements

Please refer to the Purity 6.10.3 Release Notes for detailed information on Purity security updates, improvements and fixes available in this release.