Everpure Cloud Dedicated Release Notes v6.10.6

Overview

AWS V50

Everpure Cloud Dedicated 6.10.6 introduces a new AWS V50 model for workloads that exceed the performance envelope of existing V20 configurations. The V50 SKU is designed to provide substantially higher single‑array throughput and capacity for demanding, large‑scale workloads where V20 cannot deliver sufficient IOPS and bandwidth.

The AWS V50 model uses m6in.32xlarge instances as storage controllers combined with i3en.6xlarge virtual drive instances, delivering higher backend bandwidth and IOPS than previous Everpure Cloud Dedicated AWS SKUs. Internal testing of the V50 SKU has shown that for a 70/30 mixed read/write workload with 128 KB block size and 5:1 data reduction, the array can achieve around 7 GB/s of front‑end throughput, a substantial improvement compared to V20 for similar profiles.

At launch, the Everpure Cloud Dedicated AWS V50 supports higher maximum raw capacity than V20, with design targets of up to approximately 2× the maximum capacity point of V20 when configured with two shelves of i3en.6xlarge virtual drives (up to 200 TB raw). This enables consolidation of larger datasets and more demanding workloads onto a single array while retaining core Purity data services such as snapshots, data reduction, and replication.

Functionally, the AWS V50 model supports the same Purity feature set as Everpure Cloud Dedicated AWS V20, with the following exceptions in 6.10.6:

• NVMe‑oF/TCP guest connectivity for V50 hosts is planned for a later release; at 6.10.6, V50 host connectivity uses iSCSI.

All other Purity capabilities available on Everpure Cloud Dedicated for AWS V20, including snapshots, data reduction, replication, SafeMode, and array‑level HA, remain available on the V50 model.

At 6.10.6 GA, Everpure Cloud Dedicated AWS V50 is officially supported in the following regions:

• US East (N. Virginia) – us-east-1

• US East (Ohio) – us-east-2

• US West (N. California) – us-west-1

• US West (Oregon) – us-west-2

• Europe (Ireland) – eu-west-1

• Europe (Frankfurt) – eu-central-1

• Europe (Stockholm) – eu-north-1

• Asia Pacific (Singapore) – ap-southeast-1

• Asia Pacific (Tokyo) – ap-northeast-1

• Asia Pacific (Sydney) – ap-southeast-2

• AWS GovCloud (US-West) – us-gov-west-1

Additional considerations:

• Instance capacity is per‑AZ: AWS does not guarantee m6in.32xlarge capacity in every Availability Zone of a supported region. Deployments may fail if the chosen AZ cannot satisfy the requested instance type; in such cases, selecting a different AZ or working with AWS to adjust capacity is required.

• In regions where m6in.32xlarge is unavailable, V50 selection is not hard‑blocked in the templates. Deployments in such regions will fail cleanly when AWS cannot provision the required controller instance type, instead of silently substituting another SKU.

• Some regions where m6in.32xlarge exists but Everpure Cloud Dedicated itself is not yet offered (for example, eu-south-2 / Spain) remain unsupported for V50 in this release.

AWS Reserved Instances

Alongside the new AWS V50 model, 6.10.6 adds support for deploying Everpure Cloud Dedicated AWS V50 controllers on AWS Dedicated Hosts. Customers can now choose between default (shared), dedicated instance, and dedicated host tenancy options for controller VMs at deployment time, enabling stricter physical isolation when required by security or compliance policies.

Infrastructure Encryption for Storage Account

Everpure Cloud Dedicated version 6.10.6 now facilitates migration to Azure Storage Accounts with enabled infrastructure encryption through a Customer Driven Purity Upgrade (CDU); for instance, upgrading to 6.10.6 will activate Azure Storage Account infrastructure encryption.

In supported regions, a more resilient Standard_ZRS SKU will be utilized for storage accounts.

The Purity CDU will execute an automatic storage account migration, requiring no customer intervention.

Azure VM Scale Set Flex

Introducing the Virtual Machine Scalability Sets with Flexible Orchestration (Flex) for Everpure Cloud Dedicated controller VMs to increase resiliency and availability. Placing controller VMs into different Fault Domains will protect against rack hardware failures or maintenance operations within underlying Azure host infrastructure.

Other Purity Improvements

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