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.md
+28-19Lines changed: 28 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: storage
5
5
author: normesta
6
6
7
7
ms.service: azure-blob-storage
8
-
ms.date: 05/27/2025
8
+
ms.date: 05/28/2025
9
9
ms.topic: concept-article
10
10
ms.author: normesta
11
11
---
@@ -21,30 +21,39 @@ This sample estimates the cost to retrieve a portion of data from the archive ti
21
21
22
22
Your company has an account that is located in the West US region, is configured for locally-redundant storage (LRS), and does not have hierarchical namespaces. The company has stored 20 TB of data in the archive tier for long term retention. However, after only 3 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.
23
23
24
-
## Cost components
24
+
## Costs
25
25
26
-
To analyze this data, you must first rehydrate data from the archive tier to the hot tier. You can accomplish this by changing the access tier of all blobs needed for analysis. Changing the tier from archive to hot is billed as a **read operation on the archive tier**. Moving data out of archive storage also incurs a **data retrieval fee** and because that data is retrieved before 180 days, you'll also be assessed an **early deletion fee**. Once data is moved into the hot tier, clients will need to read that data. Each blob read incurs a **read operation on the hot tier**. Aside from these cost components, rehydration time at standard priority can take up to 15 hours to complete.
26
+
The following table describes each cost that is applied in this scenario.
27
+
28
+
| Cost component | Explanation |
29
+
|----|----|
30
+
|**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 on each blob to accomplish this task. That operation is billed as a read operation on the archive tier. |
31
+
|**Data retrieval fee**| This meter applies to each GB moved from the archive tier and into an online tier such as the hot tier. |
32
+
|**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. |
33
+
|**Read from the hot tier**| Once data is moved into the hot tier, clients will need to read that data. Each blob read is billed as a read operation on the hot tier. |
34
+
35
+
Rehydration time at standard priority can take up to 15 hours to complete.
27
36
28
37
## Estimate
29
38
30
39
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.
31
40
32
-
| Cost component| Cost factor| Calculation | Value |
> 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-multi-region-access.md
+29-24Lines changed: 29 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: storage
5
5
author: normesta
6
6
7
7
ms.service: azure-blob-storage
8
-
ms.date: 05/27/2025
8
+
ms.date: 05/28/2025
9
9
ms.topic: concept-article
10
10
ms.author: normesta
11
11
---
@@ -19,36 +19,41 @@ This sample estimates the cost to upload and download data from multiple Azure r
19
19
20
20
## Scenario
21
21
22
-
Your company has a storage account that is located in the West US region, is configured for Geo-redundant storage (GRS) and does not have hierarchical namespaces enabled. This year, a new client application is being distributed to users located in multiple Azure regions across the continent. The clients will generate and upload an estimated **50,000** log files (roughly 1 GB each in size) this quarter. During this time, your company estimates that client applications will download about half of those log files for diagnostic analysis. You've been asked to create an estimate.
22
+
Your company has a storage account that is located in the West US region, is configured for Geo-redundant storage (GRS) and does not have hierarchical namespaces enabled. This year, a new client application is being distributed to users located in multiple Azure regions across the continent. Users are distributed across the continent and will 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
-
## Cost components
24
+
## Costs
25
25
26
-
Client applications incur write operations on the hot tier. Because the account is configured for Geo-redundant storage (GRS), each file that is uploaded incurs a data transfer fee and a network bandwidth fee.
27
-
Each download incurs a read cost on the hot tier. However, **75%** of those client applications are not located in the same region as the storage account so they incur a data transfer fee and a network bandwidth fee for each download.
26
+
The clients will generate and upload an estimated **50,000** log files (roughly 1 GB each in size) this quarter. During this time, your company estimates that client applications will download about half of those log files for diagnostic analysis. You've been asked to create an estimate.
27
+
28
+
| Cost component | Explanation |
29
+
|----|----|
30
+
|**Cost to write**| Based on your estimates for 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 8 MiB blocks. Each block uploaded is billed as a write operation on the hot tier. A final operation is used by the clients to commit those blocks. That operation is also billed as a write operation. 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. |
31
+
|**Cost of replication**| Because the account is configured for Geo-redundant storage, all blobs uploaded are replicated to a secondary region. This replication process adds a data transfer fee and a network bandwidth fee. This fee is charged per GB.|
32
+
|**Cost to read**| Any blob that is downloaded for diagnostic analysis is billed as a read operation on the hot tier. 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 so downloads from those clients incur a data transfer fee and a network bandwidth fee. |
28
33
29
34
## Estimate
30
35
31
36
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/)
0 commit comments