You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/azure-netapp-files-cost-model.md
+56-5Lines changed: 56 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ ms.workload: storage
13
13
ms.tgt_pltfrm: na
14
14
ms.devlang: na
15
15
ms.topic: conceptual
16
-
ms.date: 04/30/2021
16
+
ms.date: 11/4/2021
17
17
ms.author: b-juche
18
18
---
19
19
# Cost model for Azure NetApp Files
@@ -24,13 +24,63 @@ For cost model specific to cross-region replication, see [Cost model for cross-r
24
24
25
25
## Calculation of capacity consumption
26
26
27
-
Azure NetApp Files is billed on provisioned storage capacity. Provisioned capacity is allocated by creating capacity pools. Capacity pools are billed based on $/provisioned-GiB/month in hourly increments. The minimum size for a single capacity pool is 4 TiB, and capacity pools can be subsequently expanded in 1-TiB increments. Volumes are created within capacity pools. Each volume is assigned a quota that decrements from the pools-provisioned capacity. The quota that can be assigned to volumes ranges from a minimum of 100 GiB to a maximum of 100 TiB.
27
+
Azure NetApp Files is billed on provisioned storage capacity, which is allocated by creating capacity pools. Capacity pools are billed monthly based on a set cost per allocated GiB per hour. Capacity pool allocation is measured hourly.
28
28
29
-
For an active volume, capacity consumption against quota is based on logical (effective) capacity, either on active filesystem or snapshot data. A volume can only contain so much data as the set size (quota).
29
+
Capacity pools must be at least 4 TiB and can be changed in 1 TiB intervals. Capacity pools contain volumes that range in size from a minimum of 100 GiB to a maximum of 100 TiB. Volumes are assigned quotas that are subtracted from the capacity pool’s provisioned size. For an active volume, capacity consumption against the quota is based on logical (effective) capacity, being active filesystem data or snapshot data. See [How Azure NetApp Files snapshots work](.snapshots-introduction.md) for details.
30
30
31
-
The total used capacity in a capacity pool against its provisioned amount is the sum of the actual consumption of all volumes within the pool:
31
+
## Pricing examples
32
32
33
-

33
+
#### Example 1: One month cost with static versus dynamic capacity pool provisioning
34
+
35
+
If your capacity pool size requirements fluctuate (e.g. because of variable capacity or performance needs), you may want to resize your volumes and capacity pools dynamically in order to balance cost with capacity and performance needs.
36
+
37
+
Consider a scenario where you are using the standard premium capacity 24 hours (1 day) at 10 TiB, 96 hours (4 days) at 24 TiB, four times at 6 hours (1 day) at 5 TiB, 480 hours (20 days) at 6 TiB, and the month’s remaining hours at 0 TiB, a dynamic cloud consumption deployment profile looks different from a static on-premise consumption profile:
38
+
39
+

40
+
41
+
When costs are billed at $0.000403 per GiB/hour (pricing varies depending on region) the monthly cost breakdown looks like:
42
+
43
+
*Static provisioning on premium (peak capacity/performance)*
44
+
45
+
* 24 TiB x 720 hours x $0.000403 per GiB/hour = $7,130.97 per month ($237.70 per day)
46
+
47
+
*Dynamic provisioning using dynamic service level change*
48
+
49
+
* 24 TiB x 384 hours x $0.000202 per GiB/hour = $1,901.31
50
+
* 24 TiB x 120 hours x $0.000403 per GiB/hour = $1,188.50
51
+
* 24 TiB x 168 hours x $0.000538 per GiB/hour = $2,221.28
52
+
* 24 TiB x 48 hours x $0.000202 per GiB/hour = $238.29
53
+
* Total = $5,554.37
54
+
55
+

56
+
57
+
This constitutes a monthly savings of $4892.64 compared to static provisioning.
58
+
59
+
#### Example 2: One month cost with and without dynamic service level change
60
+
61
+
If your capacity pool size requirements remain the same but performance requirements fluctuate, you may want to change the service level of a volume for Azure NetApp Files dynamically. This allows you to provision and deprovision capacity pools of different types throughout the month, providing just-in-time performance, lowering costs during periods where perfomance is not needed.
62
+
63
+
Consider a scenario where the capacity requirement is a constant 24 TiB but your performance needs fluctuate between 384 hours (16 days) of standard tier, 120 hours (5 days) of premium tier, 168 hours (7 days) of ultra tier, and then back to 48 hours (2 days) of standard tier performance. In this case, a dyanmic cloud consumption deployment profile looks different from a static on-premise consumption profile:
64
+
65
+

66
+
67
+
In this case, when costs are billed at $0.000202 per GiB/hour (standard), $0.000403 per GiB/hour (premium) and $0.000538 per GiB/hour (ultra) respectively (pricing depending on region) the monthly cost breakdown looks like:
68
+
69
+
*Static provisioning on ultra tier (peak performance)*
70
+
71
+
* 24TiB x 720 hours x $0.000538 per GiB/hour = $9,519.76 per month ($317.33 per day)
72
+
73
+
*Dynamic provisioning using dynamic service level change*
74
+
75
+
24TiB x 384 hours x $0.000202 per GiB/hour = $1,901.31
76
+
24TiB x 120 hours x $0.000403 per GiB/hour = $1,188.50
77
+
24TiB x 168 hours x $0.000538 per GiB/hour = $2,221.28
78
+
24TiB x 48 hours x $0.000202 per GiB/hour = $238.29
79
+
Total = $5,554.37
80
+
81
+

82
+
83
+
This constitutes a monthly savings of $3,965.39 compared to static provisioning.
34
84
35
85
## Capacity consumption of snapshots
36
86
@@ -58,3 +108,4 @@ The following diagram illustrates the concepts.
58
108
*[Resize the capacity pool or a volume](azure-netapp-files-resize-capacity-pools-or-volumes.md)
59
109
*[Manage billing by using tags](manage-billing-tags.md)
0 commit comments