Skip to content

Commit 8ea63f9

Browse files
Incorporating feedback
1 parent 3e9ae4f commit 8ea63f9

1 file changed

Lines changed: 1 addition & 39 deletions

File tree

articles/azure-netapp-files/cool-access-introduction.md

Lines changed: 1 addition & 39 deletions
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ Cool access offers [performance metrics](azure-netapp-files-metrics.md#cool-acce
4949

5050
## Billing
5151

52-
You can enable tiering at the volume level for a newly created capacity pool. How you're billed is based on:
52+
You can enable cool access for each volume in a [cool-access enabled capacity pool](https://learn.microsoft.com/azure/azure-netapp-files/manage-cool-access). How you're billed is based on:
5353

5454
* The capacity and the service level.
5555
* Unallocated capacity within the capacity pool.
@@ -60,44 +60,6 @@ Billing calculation for a capacity pool is at the hot-tier rate for the data tha
6060

6161
The deleted data in a volume is collected once it reaches 1% of the provisioned size of the volume. This impacts the size of the cool tier, if the cool tier eligible user data is also a low percentage of the volume, such as 1~3% of the provisioned size. If the difference in the cool tier size is more than 3%, [create a support request](/azure/azure-portal/supportability/how-to-create-azure-support-request).
6262

63-
### Examples of billing structure
64-
65-
Assume that you created a 4-TiB Standard capacity pool. The billing structure is at the Standard capacity tier rate for the entire 4 TiB.
66-
67-
When you create volumes in the capacity pool and start tiering data to the cool tier, the following scenarios explain the billing structure that applies:
68-
69-
* Assume that you create three volumes with 1 TiB each. You don't enable tiering at the volume level. The billing calculation is:
70-
71-
* 3 TiB of allocated capacity at the hot tier rate.
72-
* 1 TiB of unallocated capacity at the hot tier rate.
73-
* Zero capacity at the cool tier rate.
74-
* Zero network transfer between the hot tier and the cool tier. The markup on top of the transaction cost (`GET`, `PUT`) on blob storage and private link transfer in either direction between the hot tiers determines the rate.
75-
76-
* Assume that you create four volumes with 1 TiB each. Each volume has 0.25 TiB of the volume capacity on the hot tier and 0.75 TiB of the volume capacity in the cool tier. The billing calculation is:
77-
78-
* 1-TiB capacity at the hot tier rate.
79-
* 3-TiB capacity at the cool tier rate.
80-
* Network transfer between the hot tier and the cool tier. The markup on top of the transaction cost (`GET`, `PUT`) on blob storage and private link transfer in either direction between the hot tiers determines the rate.
81-
82-
* Assume that you create two volumes with 1 TiB each. Each volume has 0.25 TiB of the volume capacity on the hot tier and 0.75 TiB of the volume capacity in the cool tier. The billing calculation is:
83-
84-
* 0.5-TiB capacity at the hot tier rate.
85-
* 2 TiB of unallocated capacity at the hot tier rate.
86-
* 1.5-TiB capacity at the cool tier rate.
87-
* Network transfer between the hot tier and the cool tier. The markup on top of the transaction cost (`GET`, `PUT`) on blob storage and private link transfer in either direction between the hot tiers determines the rate.
88-
89-
* Assume that you create one volume with 1 TiB. The volume has 0.25 TiB of the volume capacity on the hot tier and 0.75 of the volume capacity in the cool tier. The billing calculation is:
90-
91-
* 0.25-TiB capacity at the hot tier rate.
92-
* 0.75-TiB capacity at the cool tier rate.
93-
* Network transfer between the hot tier and the cool tier. The markup on top of the transaction cost (`GET`, `PUT`) on blob storage and private link transfer in either direction between the hot tiers determines the rate.
94-
95-
* Azure NetApp Files storage with cool access also enables you to only tier snapshots. For this scenario, assume you create one 1-TiB volume where 10% of the volume data is snapshots and enable cool access with the `-snapshots-only` policy. The billing calculation is:
96-
97-
* 0.9-TiB capacity at the hot tier
98-
* 0.1-TiB capacity at the cool tier
99-
* Data transfers costs occur for the initial transfer of snapshots, then network transfer costs incur only when snapshots are restored.
100-
10163
## Calculate your savings
10264

10365
Calculate your savings from cool access in the [Azure NetApp Files effective price estimator](https://aka.ms/anfcoolaccesscalc).

0 commit comments

Comments
 (0)