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
+22-21Lines changed: 22 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,50 +26,50 @@ For cost model specific to cross-region replication, see [Cost model for cross-r
26
26
27
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
-
Capacity pools must be at least 4 TiB and can be increased or decreased in 1TiB 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.
29
+
Capacity pools must be at least 4 TiB and can be increased or decreased 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
31
### Pricing examples
32
32
33
33
This section shows you examples to help you understand the Azure NetApp Files cost model.
34
34
35
35
#### Example 1: One month cost with static versus dynamic capacity pool provisioning
36
36
37
-
If your capacity pool size requirements fluctuate (for example, because of variable capacity or performance needs), you might want to resize your volumes and capacity pools dynamically in order to balance cost with capacity and performance needs.
37
+
If your capacity pool size requirements fluctuate (for example, because of variable capacity or performance needs), you might want to resize your volumes and capacity pools dynamically to balance cost with capacity and performance needs.
38
38
39
-
Consider a scenario where you are using the 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 traditional static on-premise consumption profile:
39
+
Consider a scenario where you are using the 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 traditional static on-premises consumption profile:
40
40
41
-
41
+
42
42
43
-
When costs are billed at $0.000403 per GiB/hour (pricing varies depending on the region), the monthly cost breakdown looks like the following:
43
+
When costs are billed at $0.000403 per GiB/hour (pricing varies depending on the region), the monthly cost breakdown looks like this:
44
44
45
45
*Static provisioning on Premium (peak capacity/performance)*
46
46
47
47
* 24 TiB x 720 hours x $0.000403 per GiB/hour = $7,130.97 per month ($237.70 per day)
48
48
49
49
*Dynamic provisioning using dynamic service level change*
50
50
51
-
*10TiB x 24 hours x $0.000403 per GiB/hour = $99.04
52
-
*24TiB x 96 hours x $0.000403 per GiB/hour = $950.80
53
-
*6TiB x 480 hours x $0.000403 per GiB/hour = **$1,188.50**
51
+
*10 TiB x 24 hours x $0.000403 per GiB/hour = $99.04
52
+
*24 TiB x 96 hours x $0.000403 per GiB/hour = $950.80
53
+
*6 TiB x 480 hours x $0.000403 per GiB/hour = **$1,188.50**
54
54
* Total = $2,238.33
55
55
56
-
56
+
57
57
58
-
This constitutes a monthly savings of $4892.64 compared to static provisioning.
58
+
This scenario constitutes a monthly savings of $4892.64 compared to static provisioning.
59
59
60
60
#### Example 2: One month cost with and without dynamic service level change
61
61
62
-
If your capacity pool size requirements remain the same but performance requirements fluctuate, you might want to consider [dynamically changing the service level of a volume for Azure NetApp Files](dynamic-change-volume-service-level.md). This approach allows you to provision and deprovision capacity pools of different types throughout the month, providing just-in-time performance, and lowering costs during periods where performance is not needed.
62
+
If your capacity pool size requirements remain the same but performance requirements fluctuate, consider [dynamically changing the service level of a volume for Azure NetApp Files](dynamic-change-volume-service-level.md). This approach allows you to provision and deprovision capacity pools of different types throughout the month, providing just-in-time performance, and lowering costs during periods where performance is not needed.
63
63
64
-
Consider a scenario where the capacity requirement is a constant 24 TiB but your performance needs fluctuate between 384 hours (16 days) of Standard service level, 120 hours (5 days) of Premium service level, 168 hours (7 days) of Ultra service level, and then back to 48 hours (2 days) of standard service level performance. In this case, a dynamic cloud consumption deployment profile looks different compared to a traditional static on-premise consumption profile:
64
+
Consider a scenario where the capacity requirement is a constant 24 TiB. But your performance needs fluctuate between 384 hours (16 days) of Standard service level, 120 hours (5 days) of Premium service level, 168 hours (7 days) of Ultra service level, and then back to 48 hours (2 days) of standard service level performance. In this scenario, a dynamic cloud consumption deployment profile looks different compared to a traditional static on-premises consumption profile:
65
65
66
-
66
+
67
67
68
-
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 the following:
68
+
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 the region) the monthly cost breakdown looks like this:
69
69
70
70
*Static provisioning on Ultra service level (peak performance)*
71
71
72
-
*24TiB x 720 hours x $0.000538 per GiB/hour = $9,519.76 per month ($317.33 per day)
72
+
*24 TiB x 720 hours x $0.000538 per GiB/hour = $9,519.76 per month ($317.33 per day)
73
73
74
74
*Dynamic provisioning using dynamic service level change*
75
75
@@ -79,22 +79,23 @@ In this case, when costs are billed at $0.000202 per GiB/hour (Standard), $0.000
79
79
* 24 TiB x 48 hours x $0.000202 per GiB/hour = **$238.29**
80
80
* Total = $5,554.37
81
81
82
-
82
+
83
83
84
-
This constitutes a monthly savings of $3,965.39 compared to static provisioning.
84
+
This scenario constitutes a monthly savings of $3,965.39 compared to static provisioning.
85
85
86
86
## Capacity consumption of snapshots
87
87
88
88
The capacity consumption of snapshots in Azure NetApp Files is charged against the quota of the parent volume. As a result, it shares the same billing rate as the capacity pool to which the volume belongs. However, unlike the active volume, snapshot consumption is measured based on the incremental capacity consumed. Azure NetApp Files snapshots are differential in nature. Depending on the change rate of the data, the snapshots often consume much less capacity than the logical capacity of the active volume. For example, assume that you have a snapshot of a 500-GiB volume that only contains 10 GiB of differential data.
89
+
89
90
The capacity consumption that is counted towards the volume quota for the active filesystem and snapshot would be 510 GiB, not 1000 GiB. As a general rule, a recommended 20% of capacity can be assumed to retain a week's worth of snapshot data (depending on snapshot frequency and application daily block level change rates).
90
91
91
92
The following diagram illustrates the concepts.
92
93
93
94
* Assume a capacity pool with 40 TiB of provisioned capacity. The pool contains three volumes:
94
-
* Volume 1 is assigned a quota of 20 TiB and has 13 TiB (12 TiB active, 1TiB snapshots) of consumption.
95
+
* Volume 1 is assigned a quota of 20 TiB and has 13 TiB (12 TiB active, 1-TiB snapshots) of consumption.
95
96
* Volume 2 is assigned a quota of 1 TiB and has 450 GiB of consumption.
96
-
* Volume 3 is assigned a quota of 14 TiB but has 8.8 TiB (8 TiB active, 800GiB snapshots) of consumption.
97
-
* The capacity pool is metered for 40 TiB of capacity (the provisioned amount). 22.25 TiB of capacity is consumed (13 TiB, 450 GiB and 8.8 TiB of quota from Volumes 1, 2 and 3). The capacity pool has 17.75 TiB of capacity remaining.
97
+
* Volume 3 is assigned a quota of 14 TiB but has 8.8 TiB (8 TiB active, 800-GiB snapshots) of consumption.
98
+
* The capacity pool is metered for 40 TiB of capacity (the provisioned amount). 22.25 TiB of capacity is consumed (13 TiB, 450 GiB, and 8.8 TiB of quota from Volumes 1, 2, and 3). The capacity pool has 17.75 TiB of capacity remaining.
98
99
99
100
100
101
@@ -109,4 +110,4 @@ The following diagram illustrates the concepts.
109
110
*[Resize the capacity pool or a volume](azure-netapp-files-resize-capacity-pools-or-volumes.md)
110
111
*[Manage billing by using tags](manage-billing-tags.md)
0 commit comments