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/storage/blobs/cost-estimate-archive-retrieval-copy-blob.md
+18-19Lines changed: 18 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ This sample estimates the cost to retrieve a portion of data from the archive ti
19
19
20
20
## Scenario
21
21
22
-
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've been asked to estimate what it will cost to get that data from archive storage and then download that data to clients for analysis.
22
+
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've been asked to estimate what it will cost to get that data from archive storage and then download that data to clients for analysis. Because the data is needed only temporarily, you decide that it's best to rehydrate blobs by copying them to the hot tier. That way, your company avoids the early deletion fee. After the data is no longer needed, it can be deleted from the hot tier at no charge.
23
23
24
24
The storage account is located in the West US region, is configured for locally-redundant storage (LRS), and does not have hierarchical namespaces.
25
25
@@ -29,31 +29,30 @@ The following table describes each cost.
29
29
30
30
| Cost | Description |
31
31
|----|----|
32
-
|**Change tier to hot**| First, blobs must be moved out of archive storage for analysis. To do this, administrators will change the tier of each blob from `archive`to `hot`. All tools and SDKs use the [Set Blob Tier](/rest/api/storageservices/set-blob-tier) operation to accomplish this task. That operation is billed as a read operation on the archive tier.|
32
+
|**Copy blobs to the hot tier**| First, blobs must be moved out of archive storage for analysis. To do this, administrators will copy the blob from the archive tier to the hot tier. All tools and SDKs use the [Copy Blob](/rest/api/storageservices/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|
33
33
|**Data retrieval fee**| This meter applies to each GB moved from the archive tier and into an online tier such as the hot tier. |
34
-
|**Early deletion fee**| If data is moved out of the archive tier before 180 days have transpired, a prorated early deletion fee is applied to the bill. |
35
34
|**Read from the hot tier**| Once data is moved into the hot tier, clients will need to download that data. Each download is billed as a read operation. |
36
35
37
36
## Estimate
38
37
39
38
Based on [these sample prices](blob-storage-estimate-costs.md#sample-prices), the following table shows how each cost component is calculated. This sample estimate doesn't include the [cost of data storage](blob-storage-estimate-costs.md#the-cost-to-store-data) which is billed per GB.
> You can estimate the cost of these components in your environment by using [Azure pricing calculator](https://azure.microsoft.com/pricing/calculator/) .
Copy file name to clipboardExpand all lines: articles/storage/blobs/cost-estimate-archive-retrieval-set-tier.md
+17-21Lines changed: 17 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,16 +10,16 @@ ms.topic: concept-article
10
10
ms.author: normesta
11
11
---
12
12
13
-
# Cost estimate: Retrieve data from archive storage for analysis
13
+
# Cost estimate: Move data out of archive storage
14
14
15
-
This sample estimates the cost to retrieve a portion of data from the archive tier before the 180 day limit.
15
+
This sample estimates the cost to move a portion of data from the archive tier to the hot tier before the 180 day limit.
16
16
17
17
> [!IMPORTANT]
18
18
> This estimate is based on [these sample prices](blob-storage-estimate-costs.md#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](../common/storage-plan-manage-costs.md#find-the-unit-price-for-each-meter).
19
19
20
20
## Scenario
21
21
22
-
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've been asked to estimate what it will cost to get that data from archive storage and then download that data to clients for analysis.
22
+
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 moved back to the hot tier because your company believes that this data will need to be accessed frequently. You've been asked to estimate what it will cost to get that data from archive storage and then download that data to clients for analysis.
23
23
24
24
The storage account is located in the West US region, is configured for locally-redundant storage (LRS), and does not have hierarchical namespaces.
25
25
@@ -29,31 +29,27 @@ The following table describes each cost.
29
29
30
30
| Cost | Description |
31
31
|----|----|
32
-
|**Change tier to hot**| First, blobs must be moved out of archive storage for analysis. To do this, administrators will change the tier of each blob from `archive` to `hot`. All tools and SDKs use the [Set Blob Tier](/rest/api/storageservices/set-blob-tier) operation to accomplish this task. That operation is billed as a read operation on the archive tier. |
32
+
|**Change tier to hot**| First, blobs must be moved out of archive storage. To do this, administrators will change the tier of each blob from `archive` to `hot`. All tools and SDKs use the [Set Blob Tier](/rest/api/storageservices/set-blob-tier) operation to accomplish this task. That operation is billed as a read operation on the archive tier. |
33
33
|**Data retrieval fee**| This meter applies to each GB moved from the archive tier and into an online tier such as the hot tier. |
34
34
|**Early deletion fee**| If data is moved out of the archive tier before 180 days have transpired, a prorated early deletion fee is applied to the bill. |
35
-
|**Read from the hot tier**| Once data is moved into the hot tier, clients will need to download that data. Each download is billed as a read operation. |
36
35
37
36
## Estimate
38
37
39
38
Based on [these sample prices](blob-storage-estimate-costs.md#sample-prices), the following table shows how each cost component is calculated. This sample estimate doesn't include the [cost of data storage](blob-storage-estimate-costs.md#the-cost-to-store-data) which is billed per GB.
||**Cost to retrieve**<br></br> | 4,000 blobs * $0.0220 |**$88.00**|
49
+
|**Early deletion fee**| Rough number of months penalty | (180 days - 90 days) / 30 days | 3 |
50
+
|| Price per month of archive storage (per GB) || $0.0020 |
51
+
||**Cost of early deletion**<br></br> | (4000 blobs * $0.0020) * 3 |**$24.00**|
52
+
|**Total cost**|| $0.22 + $88 + $24 |**$112.22**|
57
53
58
54
> [!TIP]
59
55
> You can estimate the cost of these components in your environment by using [Azure pricing calculator](https://azure.microsoft.com/pricing/calculator/) .
0 commit comments