Skip to main content
Keystone
3.0

Keystone billing for specific volume types

Contributors netapp-shwetav netapp-manini netapp-aruldeepa netapp-bcammett

Keystone 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.

The following table summarizes the billing rules for each volume type.

Volume type Billing rule

Cloned volumes

Billed as standard volumes

Temporary volumes

Not billed

SnapMirror destinations

Billed at the destination performance service level

LUNs

Billed at the performance service level of the containing volume

System and root volumes

Monitored but not billed

Billing for cloned volumes

Cloned volumes are billed as standard volumes at the same performance service level as the volume they were cloned from. All cloned volumes are measured and charged regardless of their size or purpose.

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 for SnapMirror destinations

The pricing for SnapMirror destination volumes, whether used for disaster recovery or long-term retention, is based on the performance service level assigned to the destination. There is no extra fee for data protection.

Billing for LUNs

For LUNs, the billing is based on the performance service levels of 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.