Capacity requirements and adjustments in Keystone
Suggest changes
PDFs
The minimum capacity requirements and incremental increases for Keystone STaaS performance service levels differ by storage type. This page also describes how committed capacity can be increased, decreased, or reallocated during the subscription term.
Minimum capacity requirements for unified and block-optimized storage
You can see the minimum capacity and incremental capacity allowed per subscription for unified and block-optimized storage in the following tables:
Unified storage
Capacity |
Extreme |
Premium |
Standard |
Value |
Minimum capacity per PSLI [in TiB] |
50 |
100 |
||
Incremental capacity (and in multiples) allowed at start of subscription [in TiB] |
25 |
|||
Incremental capacity (and in multiples) allowed as add-on during subscription [in TiB] |
25 |
|||
Block optimized storage
Capacity |
Extreme |
Premium |
Standard |
Minimum capacity per PSLI [in TiB] |
50 |
50 |
100 |
Incremental capacity (and in multiples) allowed at start of subscription [in TiB] |
25 |
||
Incremental capacity (and in multiples) allowed as add-on during subscription [in TiB] |
25 |
||
The minimum capacity for each performance service level is the same across all Keystone sales.
Minimum capacity requirements for AFX storage
You can see the minimum capacity requirements for AFX storage in the following table:
Capacity |
Extreme |
Minimum capacity [in TiB] per AFX cluster |
200 |
Incremental capacity (and in multiples) allowed at start of subscription [in TiB] |
100 |
Incremental capacity (and in multiples) allowed as add-on during subscription [in TiB] |
100 |
|
For AFX storage, capacity is committed and measured at the AFX cluster level, across all drive shelves in the cluster. This is independent of the number of AFX storage controllers in the cluster. |
Minimum capacity requirements for object storage
You can see the minimum capacity requirements for object storage in the following table:
Capacity |
Standard |
Value |
Minimum capacity [in TiB] per order |
200 |
500 |
Incremental capacity (and in multiples) allowed at start of subscription [in TiB] |
25 |
100 |
Incremental capacity (and in multiples) allowed as add-on during subscription [in TiB] |
25 |
100 |
Minimum capacity requirements for cloud services
You can see the minimum capacity requirements for cloud services in the following table:
Capacity |
Cloud Volumes ONTAP |
Minimum capacity [in TiB] per order |
4 |
Incremental capacity (and in multiples) allowed at start of subscription [in TiB] |
1 |
Incremental capacity (and in multiples) allowed as add-on during subscription [in TiB] |
1 |
Capacity adjustments
Communicate any planned capacity changes to NetApp in a timely manner to allow for planning and deployment. The following conditions apply to all capacity adjustments:
-
Capacity increases: Committed capacity can be increased during the subscription term in the specified increments, except within the last 90 days before expiry unless the subscription is being renewed. Once confirmed by NetApp, the increase applies for the remainder of the term and the minimum payment is revised accordingly. All capacity additions and new services, whether on-premises or cloud, co-term with the existing subscription. Committed capacity for cloud services cannot be reduced at any point during the subscription term.
-
Billing for increases: For subscriptions on the Annual in Advance payment model, NetApp will invoice for any pro-rated increase in minimum payments owed for the remainder of the current billing period. The invoice sent following the activation of the new services reflects the revised billing.
-
Burst capacity: Additional capacity above the committed level is available at each site, typically up to 20% per performance service level. For details on burst limits and billing, see Supported storage capacities in Keystone.
-
Performance service level changes: Increasing to a higher performance service level is allowed during the subscription term. Reducing to a lower performance service level is not permitted.
-
On-premises capacity reduction: Committed capacity for on-premises services can be reduced under certain conditions. See Capacity reduction for details.
Capacity reduction
Committed capacity reduction applies to the Annual in Advance payment model and on-premises Keystone deployments only. A minimum subscription term of 24 months is required to be eligible. Cloud services and hybrid cloud deployments are not eligible for capacity reduction.
The following conditions govern all committed capacity reduction requests:
-
Written request: Requests must be submitted in writing and received by NetApp at least 60 days before the next annual subscription period in which the reduction takes effect.
-
Permitted reductions per term:
-
For 2- or 3-year subscription terms: one reduction is permitted during the subscription term.
-
For 4- or 5-year subscription terms: two reductions are permitted during the subscription term.
-
-
Reduction cap per request: A single reduction cannot exceed 25% of the committed capacity at the time of the request.
-
Minimum capacity threshold: A reduction cannot cause the committed capacity to fall below the minimum committed capacity requirement for the applicable performance service level.
-
Effective date: Approved reductions take effect at the start of the next annual subscription period.
For a reduction request to be approved, the on-premises service-based annual payments must remain at or above USD 200K after the reduction is applied.
The following image shows an example of how capacity reductions apply to a 3-year Keystone subscription.
In this example, the initial committed capacity is 300 TiB (USD 300K annual payment). In year 1, a request to reduce capacity to 225 TiB is received. NetApp validates the reduction (75 TiB) is within the 25% cap and the resulting payment stays at or above USD 200K. The request is approved and takes effect at the start of year 2. In year 2, a request to reduce capacity to 100 TiB is received. NetApp declines the request because the reduction exceeds 25% of the current committed capacity (225 TiB) and the one permitted reduction for this 3-year term has already been used. Capacity for year 3 remains at 225 TiB (USD 225K annual payment), and no further reductions are permitted.
Quarterly spend reallocation
Quarterly spend reallocation is available for hybrid cloud services only. It allows you to reallocate on-premises service spend to cloud services spend on a quarterly basis. Reallocation from cloud services back to on-premises is not permitted.
The following conditions apply to all reallocation requests:
-
Reallocation limit: Up to 25% of the annual contract value (ACV) at the time of the request can be reallocated.
-
Minimum payment after reallocation: Post-reallocation, the on-premises monthly minimum payment per subscription must remain at or above USD 16,667.
-
90-day lock: A new reallocation request cannot be activated until at least 90 days after the activation of the previous reallocation.
-
End-of-term restriction: Reallocation is not permitted during the last 90 days of the subscription term, unless the subscription is being renewed.
-
Request deadline: Requests must be submitted at least 5 business days before the next billing cycle.
-
Effective date: Approved requests take effect on the first day of the next billing cycle.
The following image illustrates how quarterly spend reallocation works.
In this example, on-premises spending is USD 30K/month. In February, Request A to move USD 5K to cloud services is approved and activated in March, triggering a 90-day lock through May. Request B, submitted during the lock period, activates after the lock expires, reducing on-premises spend to USD 20K and increasing cloud services spend to USD 10K from July. No reallocation is permitted in the last 90 days of the term.
This table provides a set of sample values to demonstrate how the reallocation of expenses works. In this example, USD 5,000 from the monthly spend is reallocated to hybrid cloud storage service.
Before allocation |
Capacity (TiB) |
Monthly designated expense |
Extreme |
125 |
37,376 |
After reallocation |
Capacity (TiB) |
Monthly designated expense |
Extreme |
108 |
37,376 |
Cloud Volumes ONTAP |
47 |
5,000 |
37,376 |
The reduction is of (125-108) = 17 TiB of the capacity allocated for the Extreme performance service level. On spend reallocation, the allotted hybrid cloud storage is not of 17 TiB but an equivalent capacity that $5000 can purchase. In this example, for $5000, you can get 17 TiB on-prem storage capacity for the Extreme performance service level and 47 TiB hybrid cloud capacity of Cloud Volumes ONTAP performance service level. Therefore, the reallocation is with respect to the spend, not capacity.
Contact your Keystone Success Manager (KSM) to submit a reallocation request.