Evergreen//One and Everpure Cloud Dedicated Array capacity

Everpure Cloud Dedicated for AWS
Audience
Public
Technology Integrations
Amazon Web Services (AWS)
Source Type
Documentation

Overview

Everpure Evergreen//One (EG1) and Everpure Cloud Dedicated use Effective Used Capacity (EUC) as the unit of measure for subscription billing. At a high level, this means licensing and billing are tied to the amount of customer data stored (effective used), not to the raw or usable capacity of any individual array.

At the same time, each Everpure Cloud Dedicated array has a fixed usable capacity defined by its capacity point and underlying cloud storage configuration (for example, a capacity point with 4.65 TiB usable / 18.6 TiB effective @ 4:1). As a result, an environment can have spare EG1 license capacity while a specific Everpure Cloud Dedicated array is still physically full.

EG1 Licensed Capacity

With EG1 and Everpure Cloud Dedicated, capacity is licensed and billed on Effective Used Capacity (EUC):

  • EUC represents the amount of host data written before deduplication and compression, counting only unique data from snapshots and clones.

  • EG1 commitments and usage are tracked in TiB of EUC, not in raw or usable capacity of an individual array.

  • This model applies whether Everpure Cloud Dedicated is consumed via a direct Evergreen//One subscription or via a cloud marketplace; marketplace offers still use EG1 and EUC metering in the background.

In other words, an EG1 subscription defines how much effective customer data is under contract across the service, independent of how many Everpure Cloud Dedicated arrays are deployed or how large any single array is.

Everpure Cloud Dedicated Array Capacity

Each Everpure Cloud Dedicated array has its own physical usable capacity limit based on its capacity point:

  • Capacity points define total usable TiB per model (for example, 4.65 TiB usable, 18.6 TiB effective at 4:1), corresponding to a specific Everpure Cloud Dedicated capacity point in the chosen cloud environment.

  • This usable capacity is the hard ceiling for how much data the array can store after data reduction and internal overheads.

Once a 4.65 TiB usable Everpure Cloud Dedicated array reaches that limit, it cannot accept additional data, even if the EG1 subscription still has unused TiB available.

Example

Consider a deployment with:

  • An EG1 subscription committing to 50 TiB of EUC.

  • A Everpure Cloud Dedicated array deployed at the 4.65 TiB usable / 23.25 TiB effective (5:1) capacity point.

As data grows:

  • From a licensing perspective, the deployment remains within the EG1 subscription as long as total effective used capacity across the service is within the 50 TiB EUC commitment (plus any allowed overage).

  • From an array perspective, the Everpure Cloud Dedicated system becomes constrained once it approaches 4.65 TiB usable, regardless of the remaining EG1 entitlement.

The impact of data reduction is visible on the infrastructure side:

  • If 50 TiB of EUC were stored with little or no data reduction (1:1), it would require 50 TiB of usable capacity across Everpure Cloud Dedicated arrays, driving higher underlying cloud storage cost.

  • If the same 50 TiB of EUC achieved 5:1 data reduction, it would require only 10 TiB of usable capacity, lowering the infrastructure footprint and cost for the same licensed EUC.

In all of these cases, the EG1 charge is still based on 50 TiB of EUC; data reduction primarily affects how much Everpure Cloud Dedicated usable capacity and cloud infrastructure are required to support that licensed amount.

Key Points for planning

  • EG1 license capacity (EUC) reflects the amount of data under subscription, not the size of an individual Everpure Cloud Dedicated array.

  • Everpure Cloud Dedicated usable capacity is a physical limit per array and can be smaller than the EG1 subscription size; when an array becomes full or approaches its usable capacity threshold, it still needs more array capacity, even if the EG1 subscription shows unused TiB.

  • Everpure Cloud Dedicated supports capacity expansion by capacity points, including:

    • Customer‑driven capacity upgrades, where additional capacity points are added non‑disruptively when more usable capacity is needed.

    • Automatic Capacity Upgrade (only on Azure, when enabled), which can automatically add the next capacity point after a utilization threshold (for example, ~80% used) is reached, making Everpure Cloud Dedicated behave more like an elastic service. This will still incur additional underlying cloud cost for each expansion.

  • Capacity planning should always consider both:

    • Overall EG1 effective used capacity (for licensing and billing), and

    • Per‑array Everpure Cloud Dedicated capacity points and expansion options (for operational headroom, non‑disruptive growth, and infrastructure cost).