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
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,11 +19,11 @@ 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.
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're asked to estimate the cost to get that data from archive storage and then download that data to clients.
23
23
24
24
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](cost-estimate-archive-retrieval-set-tier.md) 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.
25
25
26
-
The storage account is located in the West US region, is configured for locally-redundant storage (LRS), and does not have hierarchical namespaces.
26
+
The storage account is located in the West US region, is configured for locally-redundant storage (LRS), and doesn't have hierarchical namespaces.
27
27
28
28
## Costs
29
29
@@ -33,7 +33,7 @@ The following table describes each cost.
33
33
|----|----|
34
34
|**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](/rest/api/storageservices/copy-blob) operation to accomplish this task. The [Copy Blob](/rest/api/storageservices/copy-blob) operation is billed as a read operation on the source account and a write operation on the destination account. |
35
35
|**Data retrieval fee**| This meter applies to each GB moved from the archive tier and into an online tier such as the hot tier. |
36
-
|**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
+
|**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. |
37
37
38
38
## Estimate
39
39
@@ -57,7 +57,7 @@ Based on [these sample prices](blob-storage-estimate-costs.md#sample-prices), th
> This scenario does not model the amount of time that data exists in the storage, so the table does not include [cost of data storage](blob-storage-estimate-costs.md#the-cost-to-store-data) which is billed per GB. You can estimate the cost storage and the cost of transactions in your environment by using [Azure pricing calculator](https://azure.microsoft.com/pricing/calculator/).
60
+
> 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](blob-storage-estimate-costs.md#the-cost-to-store-data) which is billed per GB. You can estimate the cost storage and the cost of transactions 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
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,17 +19,17 @@ This sample estimates the cost to move a portion of data from the archive tier t
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 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.
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. You are asked to estimate the cost to get that data from archive storage.
23
23
24
-
The storage account is located in the West US region, is configured for locally-redundant storage (LRS), and does not have hierarchical namespaces.
24
+
The storage account is located in the West US region, is configured for locally-redundant storage (LRS), and doesn't have hierarchical namespaces.
25
25
26
26
## Costs
27
27
28
28
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. 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 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
35
@@ -48,11 +48,11 @@ Based on [these sample prices](blob-storage-estimate-costs.md#sample-prices), th
48
48
||**Cost to retrieve**<br></br> | 4,000 blobs * $0.0220 |**$88.00**|
49
49
|**Early deletion fee**| Rough number of months penalty | (180 days - 90 days) / 30 days | 3 |
50
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**|
51
+
||**Cost of early deletion**<br></br> | (4,000 blobs * $0.0020) * 3 |**$24.00**|
52
52
|**Total cost**|| $0.22 + $88 + $24 |**$112.22**|
53
53
54
54
> [!TIP]
55
-
> This scenario does not model the amount of time that data exists in storage, so the table does not include [cost of data storage](blob-storage-estimate-costs.md#the-cost-to-store-data) which is billed per GB. You can estimate the cost storage and the cost of transactions in your environment by using [Azure pricing calculator](https://azure.microsoft.com/pricing/calculator/).
55
+
> This scenario doesn't model the amount of time that data exists in storage, so the table doesn't include [cost of data storage](blob-storage-estimate-costs.md#the-cost-to-store-data) which is billed per GB. You can estimate the cost storage and the cost of transactions 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-multi-region-access.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,19 +19,19 @@ This sample estimates the cost to upload and download data from multiple Azure r
19
19
20
20
## Scenario
21
21
22
-
Your company plans to distribute a new client application to users located in multiple Azure regions across the continent. This application will be used to upload log files and download them for diagnostic analysis. Files are stored as blobs in the hot access tier. Based on expected usage patterns, you've been asked to create a rough estimate of costs.
22
+
Your company plans to distribute a new client application to users located in multiple Azure regions across the continent. This application is used to upload log files and download them for diagnostic analysis. Files are stored as blobs in the hot access tier. Based on expected usage patterns, you've been asked to create a rough estimate of costs.
23
23
24
-
The storage account is located in the West US region, is configured for Geo-redundant storage (GRS) and does not have hierarchical namespaces enabled.
24
+
The storage account is located in the West US region, is configured for Geo-redundant storage (GRS) and doesn't have hierarchical namespaces enabled.
25
25
26
26
## Costs
27
27
28
28
The following table describes each cost.
29
29
30
30
| Cost | Description |
31
31
|----|----|
32
-
|**Cost to write**| During this quarter, clients will upload an estimated **50,000** log files (roughly **1 GB** each in size). Clients are configured to upload those log files in 8MiB blocks. Each block is billed as a write operation with one additional operation to commit those blocks. A smaller block size is very performant, but you know that a larger block size results in fewer write operations so you plan to include that suggestion along with your estimate. |
32
+
|**Cost to write**| During this quarter, clients upload an estimated **50,000** log files (roughly **1 GB** each in size). Clients are configured to upload those log files in 8-MiB blocks. Each block is billed as a write operation with one additional operation to commit those blocks. A smaller block size is performant, but you know that a larger block size results in fewer write operations so you plan to include that suggestion along with your estimate. |
33
33
|**Cost of replication**| Because the account is configured for geo-redundant storage, all blobs are replicated to a secondary region. This replication process adds a data transfer fee per GB replicated.|
34
-
|**Cost to read**| Any blob that is downloaded for diagnostic analysis is billed as a read operation. You believe that client applications will download about half of the files uploaded for diagnostic analysis. You also learn that **75%** of client applications are not located in the same region as the storage account. Therefore, blobs downloaded by those clients incur a network bandwidth fee. |
34
+
|**Cost to read**| Any blob that is downloaded for diagnostic analysis is billed as a read operation. You believe that client applications will download about half of the files uploaded for diagnostic analysis. You also learn that **75%** of client applications aren't located in the same region as the storage account. Therefore, blobs downloaded by those clients incur a network bandwidth fee. |
35
35
36
36
## Estimate
37
37
@@ -54,7 +54,7 @@ Based on [these sample prices](blob-storage-estimate-costs.md#sample-prices), th
> This scenario does not model the amount of time that data exists in storage, so the table does not include [cost of data storage](blob-storage-estimate-costs.md#the-cost-to-store-data) which is billed per GB. You can estimate the cost storage and the cost of transactions in your environment by using [Azure pricing calculator](https://azure.microsoft.com/pricing/calculator/).
57
+
> This scenario doesn't model the amount of time that data exists in storage, so the table doesn't include [cost of data storage](blob-storage-estimate-costs.md#the-cost-to-store-data) which is billed per GB. You can estimate the cost storage and the cost of transactions in your environment by using [Azure pricing calculator](https://azure.microsoft.com/pricing/calculator/).
0 commit comments