Skip to main content
Keystone
2.0
A newer release of this product is available.

Keystone STaaS billing for specific volume types

Contributors netapp-shwetav
PDFs

Keystone STaaS billing rules differ for certain volume configurations. Knowing these exceptions helps you avoid unexpected charges when working with cloned volumes, SnapMirror destinations, LUNs, or temporary storage.

Billing for cloned volumes

If volumes are cloned in ONTAP and you use them for backing up and restoring your data, you can continue using the clones without any additional payments. However, cloned volumes used for any other purpose in your business for an extensive duration are charged.

Note the following:

  • Clone volumes are free from charging as long as their size is less than 10% of the parent volume (the physical capacity used in the clone volume compared to the physical capacity used in the parent volume).

  • There is no 24-hour grace period for cloned volumes. Only the size of the clone is considered.

  • Once the clone volume exceeds 10% of the physical size of the parent, the clone is billed as a standard volume (logical used capacity).

Billing for temporary volumes

Occasionally, temporary (TMP) volumes are created by ONTAP when moving volumes. These temporary volumes are short-lived, and the consumption on these volumes is not measured for billing.

Billing and adaptive QoS policies

Keystone measures consumption based on service levels. Each service level is associated with a specific adaptive quality of service (QoS) policy. During deployment, you will be informed of the details of each adaptive QoS policy for your subscribed Keystone services. During storage management operations, ensure that your volumes have the appropriate adaptive QoS policies assigned as per your subscribed service levels to avoid unexpected billing.
For more information about adaptive QoS policies in ONTAP, see Guarantee throughput with QoS overview.

Billing for SnapMirror destinations

The pricing for the SnapMirror destination volume is governed by the adaptive QoS policy for the service level assigned on the source. However, if the source does not have an associated adaptive QoS policy, the destination is billed based on the lowest available service level.

Billing for LUNs

For LUNs, the same billing pattern is followed as for the volumes that are governed by adaptive QoS policies. If separate adaptive QoS policies are set on LUNs, then:

  • The size of the LUN is counted for consumption according to the associated service level of that LUN.

  • The remainder of the space in the volume, if any, is charged according to the adaptive QoS policy of the service level set on the volume.

System and root volumes

System and root volumes are monitored as a part of the overall monitoring of the Keystone service but are not counted or billed. The consumption on these volumes is exempted for billing.