Skip to main content
Keystone
3.0

Storage capacity types in Keystone

Contributors netapp-shwetav netapp-manini netapp-aruldeepa netapp-bcammett netapp-manishc
PDFs

Keystone STaaS uses several capacity terms to measure, commit, and bill for storage. Understanding these terms will help you plan your subscription and interpret your usage reports and invoices.

Logical capacity

This is the amount of storage capacity required to store user data before any data efficiencies provided by the storage array are applied.

Committed capacity

The minimum logical capacity billed each month during the subscription:

  • Capacity is committed to each performance service level instance for unified or block-optimized storage, or per AFX cluster.

  • Committed capacity and additional performance service levels can be added during the term.

Changes to committed capacity

During a subscription, you can change committed capacities subject to certain conditions. For full details on capacity increase and decrease rules, see Capacity requirements for Keystone performance service levels. To request a change, contact your Keystone Success Manager (KSM) or NetApp support.

Consumed capacity

Consumed capacity refers to the capacity (in TiB of storage) currently being consumed on the service. It is calculated differently based on the data storage type:

  • Unified or block-optimized storage: Consumed capacity is calculated based on the type of capacity (either logical or physical) selected during the ordering process. The calculation is performed per performance service level instance.

    1. Logical capacity: It is the sum of:

      • Metered logical capacity, before storage array data efficiencies, to store all instances and types of customer data, such as copies, mirrored copies, versions, and clones.

      • Physical capacity used to store metadata and differential data of snapshots and certain clones.

      • Any thick-provisioned physical capacity.

    2. Physical capacity: It is the sum of:

      • Metered physical capacity, after storage array data efficiencies, to store all instances and types of customer data, such as copies, mirrored copies, versions, and clones.

      • Physical capacity used to store metadata and differential data of snapshots.

      • Any thick-provisioned physical capacity.

  • AFX storage: It is calculated per AFX cluster as the sum of:

    • Metered physical capacity, after storage array data efficiencies, to store all instances and types of customer data, such as copies, mirrored copies, versions, and clones.

    • Physical capacity used to store metadata and differential data of snapshots.

    • Any thick-provisioned physical capacity.

  • Object storage: Consumed capacity is calculated as the amount of metered physical capacity used to store all instances and types of customer data across all nodes. This calculation is based on the information lifecycle management (ILM) policies configured.

  • Cloud Volumes ONTAP: Consumed capacity is calculated as the amount of metered provisioned logical capacity of all Cloud Volumes ONTAP volumes.

Burst capacity

The NetApp Keystone STaaS service enables you to use additional capacity on top of the committed capacity for a performance service level. This is referred to as the burst capacity usage.

Note these points:

  • Burst capacity limit is agreed upon in the Keystone order. It is usually set to a default of 20% above the committed capacity per performance service level instance or per AFX cluster, with additional options available for unified and block-optimized storage to select burst capacity limits of 40% or 60% of committed capacity.

  • Burst capacity consumption is invoiced at the same rate as the committed capacity corresponding to the selected data storage type (DST) and performance service level.

  • Keystone STaaS services provide a burst waiver period of 60 days from the start date.

Billed capacity

Monthly bill = (committed capacity [TiB] * committed rate [$/TiB]) + (daily average provisioned burst capacity [TiB] * burst rate [$/TiB]). The monthly bill contains a minimum charge based on the committed capacity.

The monthly bill varies beyond the minimum charge based on daily average burst capacity consumption.