你当前正在访问 Microsoft Azure Global Edition 技术文档网站。 如果需要访问由世纪互联运营的 Microsoft Azure 中国技术文档网站,请访问 https://docs.azure.cn。
This sample estimates the cost to retrieve a portion of data from the archive tier before the 180 day limit.
Important
This estimate is based on these sample prices. Sample prices shouldn't be used to calculate your production costs. To find official prices, see Find the unit price for each meter.
Scenario
Your company stores 20 TB of data in the archive tier for long term retention. However, after only three months in archive storage, 20% of that data must be retrieved for analysis. You're asked to estimate the cost to get that data from archive storage and then download that data to clients.
Because the data is needed only temporarily, you decide not to rehydrate blobs by changing their tier. That way, your company avoids the early deletion fee. You already estimated the cost of that approach by reviewing the Cost estimate: Move data out of archive storage article. Instead, you decide that it's more cost-effective to copy blobs into the hot tier for analysis. You know that data in the hot tier can be deleted at no charge when the analysis is complete.
The storage account is located in the West US region, is configured for locally-redundant storage (LRS), and doesn't have hierarchical namespaces.
Costs
The following table describes each cost.
Cost | Description |
---|---|
Copy blobs to the hot tier | First, blobs must be moved out of archive storage for analysis. All tools and SDKs use the Copy Blob operation to accomplish this task. The Copy Blob operation is billed as a read operation on the source account and a write operation on the destination account. |
Data retrieval fee | This meter applies to each GB moved from the archive tier and into an online tier such as the hot tier. |
Read from the hot tier | Once data is moved into the hot tier, clients need to download that data. Each download is billed as a read operation. |
Estimate
Based on these sample prices, the following table shows how each cost component is calculated. This sample estimate doesn't include the cost of data storage which is billed per GB.
Cost | Cost factor | Calculation | Value |
---|---|---|---|
Copy blobs to the hot tier | Number of Copy Blob operations | 2000 blobs * 20% | 400 |
Price of an archive read operation | $0.00055 | ||
Cost to read from the archive | 400 operations * $0.00055 | $0.22 | |
Price of a hot tier write operation | $0.0000055 | ||
Cost to write to the hot tier | 400 operations * $0.0000055 | $0.0022 | |
Cost to copy blobs to hot tier |
$0.22 + $0.0022 | $0.22 | |
Data retrieval fee | Total file size | 20,000 GB | |
Data retrieval size | 20,000 GB * 20% | 4,000 | |
Price of data retrieval (per GB) | $0.0220 | ||
Cost to retrieve |
4,000 blobs * $0.0220 | $88.00 | |
Read from hot tier | Number of read operations on hot tier | The number of blobs moved to hot tier | 400 |
Price of a read operation on the hot tier | $0.00000044 | ||
Cost to read from hot tier |
400 operations * $0.00000044 | $0.0002 | |
Total cost | $0.22 + $88 + $24 + $0.0002 | $88.22 |
Tip
This scenario doesn't model the amount of time that data exists in the storage, so the table doesn't include cost of data storage which is billed per GB. You can estimate the cost storage and the cost of transactions in your environment by using Azure pricing calculator.