Skip to content

Commit cf84e93

Browse files
committed
rm cool access text
1 parent e567ae6 commit cf84e93

File tree

1 file changed

+0
-8
lines changed

1 file changed

+0
-8
lines changed

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

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -84,14 +84,6 @@ Azure NetApp Files storage with cool access is supported for the following regio
8484
* West US 2
8585
* West US 3
8686

87-
88-
Assume a case where 10% of all the data that a customer has is coming from snapshots. In that case 90% of the total pool capacity will be priced based on the standard/premium/ultra (whichever is the pool type, you can use any of these), and remaining 10% is priced based on the cool access rate. Data transfer cost will be for the initial transfer of snapshots. Then network cost will only happen when snapshots are restored. Assume 50% snapshot data restore happening once in 6 month or a year. The total saving can be estimated for 6 months and a year.
89-
90-
* Assume a Premium standard service level pool where 10% of the data is from [snapshots](snapshots-introduction.md). In this scenario, 90% of the total capacity pool pricing is based on the Premium service level, and the remaining 10% is based on the cool access rate.
91-
92-
Data transfers costs exist for the initial transfer of snapshots, then network costs incur _only_ when snapshots are restored.
93-
94-
9587
## Metrics
9688

9789
Cool access offers [performance metrics](azure-netapp-files-metrics.md#cool-access-metrics) to understand usage patterns on a per-volume basis:

0 commit comments

Comments
 (0)