Skip to content

Commit cf6f30a

Browse files
normestanormesta
committed
Some more tweaks
1 parent ef4f6b3 commit cf6f30a

File tree

2 files changed

+35
-43
lines changed

2 files changed

+35
-43
lines changed

‎articles/storage/blobs/cost-estimate-archive-retrieval.md

Lines changed: 6 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: 'Cost estimate: Early retrieval from archive (Azure Blob Storage)'
3-
description: This article shows an example of what it costs to archive and then retrieve data in Azure Blob Storage.
2+
title: 'Cost estimate: Analyze archived data (Azure Blob Storage)'
3+
description: This article shows an example of what it costs to retrieve and analyze archived data in Azure Blob Storage.
44
services: storage
55
author: normesta
66

@@ -10,7 +10,7 @@ ms.topic: concept-article
1010
ms.author: normesta
1111
---
1212

13-
# Cost estimate: Early data retrieval from archive
13+
# Cost estimate: Retrieve data from archive storage for analysis
1414

1515
This sample estimates the cost to retrieve a portion of data from the archive tier before the 180 day limit.
1616

@@ -21,13 +21,9 @@ This sample estimates the cost to retrieve a portion of data from the archive ti
2121

2222
Your 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. The account is located in the West US region, and is configured for locally-redundant storage (LRS), and hierarchical namespaces are not enabled.
2323

24-
## Cost factors
24+
## Cost components
2525

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**.
27-
28-
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**.
29-
30-
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+
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.
3127

3228
## Estimate
3329

@@ -47,7 +43,7 @@ Based on [these sample prices](blob-storage-estimate-costs.md#sample-prices), th
4743
| | Cost of early deletion<br></br> | (4000 blobs * $0.0020) * 3 | **$24.00** |
4844
| **Read from hot tier** | Number of read operations on hot tier | The number of blobs moved to hot tier | 400 |
4945
| | Price of a read operation on the hot tier | Taken from sample prices | $0.00000044 |
50-
| | Cost to read blobs from the hot tier<br></br> | 400 operations * $0.00000044 | $0.0002 |
46+
| | Cost to read blobs from the hot tier<br></br> | 400 operations * $0.00000044 | **$0.0002** |
5147
| **Total cost** | | | **$112.22** |
5248

5349
> [!TIP]

‎articles/storage/blobs/cost-estimate-multi-region-access.md

Lines changed: 29 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: storage
55
author: normesta
66

77
ms.service: azure-blob-storage
8-
ms.date: 05/14/2025
8+
ms.date: 05/27/2025
99
ms.topic: concept-article
1010
ms.author: normesta
1111
---
@@ -19,43 +19,39 @@ This sample estimates the costs associated with uploading and downloading data f
1919
2020
## Scenario
2121

22-
In this scenario, client applications are located in different Azure regions across the continent. These client applications generate and upload **50,000** log files. Each file is **1 GB** in size. 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.
22+
Your company has a storage account that is located in the West US region and hierarchical namespaces are not 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 this quarter. Each file is **1 GB** in size. During the quarter, 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.
2323

24-
Client applications download about half of those log files for diagnostic analysis. 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.
24+
## Cost components
2525

26-
The account is located in the West US region and hierarchical namespaces are not enabled.
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.
2728

2829
## Estimate
2930

30-
Based on [these sample prices](blob-storage-estimate-costs.md#sample-prices), the following table shows how each cost component is calculated.
31-
32-
| Cost factor | Calculation | Value |
33-
|-------------------------------------------------------|----------------------------------------------|-------------|
34-
| PutBlock operations per blob | 1 GiB / 8-MiB block | 155 |
35-
| PutBlockList operations per blob | 1 per blob | 1 |
36-
| **Cost of write operations** | (50,000 blobs * 156) * write operation price | **$163.80** |
37-
| Data transfer fee (replication) | 50,000 GB * data transfer fee | $1,000.00 |
38-
| Network bandwidth fee (replication) | 50,000 GB * network bandwidth fee | $1,000.00 |
39-
| **Cost to transfer data out of region (replication)** | data transfer fee + network bandwidth fee | **$2,000** |
40-
| Number of read operations | 50,000 / 2 | 25,000 |
41-
| **Cost of read operations** | 25,000 GB * read operation price | **$110.00** |
42-
| Number of blobs downloaded from other regions | 25,000 * 75% | 1875 |
43-
| Data transfer fee (downloads) | 1875 * data transfer fee | $375.00 |
44-
| Network bandwidth fee (downloads) | 1875 * network bandwidth fee | $375.00 |
45-
| **Cost to transfer data out of region (download)** | data transfer fee + network bandwidth fee | **$750.00** |
46-
| **Total cost** | write + read + data transfer | **860.00** |
47-
48-
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.
49-
50-
## Factors that can impact the cost
51-
52-
The following table describes factors that can impact the cost of this scenario.
53-
54-
| Factor | Impact | Learn more |
55-
|---|---|----|
56-
| Block size | Larger block size reduces the number of write operations required to upload data. | [The cost to upload data](blob-storage-estimate-costs.md) |
57-
| Uploading data by using the Data Lake Storage endpoint | Smaller fixed block sizes of 4 MiB increases the number of write operations. | [Cost of uploading to the Data Lake Storage endpoint](azcopy-cost-estimation.md#cost-of-uploading-to-the-data-lake-storage-endpoint) |
58-
| Redundancy configuration of the account | Storage redundancy configuration impacts the cost of certain operations. For example, you could configure your account for read-access geo-zone-redundant storage (RA-GZRS) which enables clients to download from either the primary or secondary regions. However, moving the RA-GZRS changes the price of certain operations. | [Azure Storage redundancy](../common/storage-redundancy.md) |
31+
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.
32+
33+
| Cost component | Cost factor | Calculation | Value |
34+
|-------------------------|-----------------------------------------------|--------------------------------------|---------------|
35+
| **Cost to write** | PutBlock operations per blob | 1 GiB / 8-MiB block | 155 |
36+
| | PutBlockList operations per blob | 1 per blob | 1 |
37+
| | Price of a write operation on the hot tier | Taken from sample prices | $0.0000210000 |
38+
| | Cost to upload log files<br></br> | (50,000 blobs * 156) * $0.0000210000 | **$163.80** |
39+
| **Cost of replication** | Price of data transfer (per GB) | Taken from sample prices | $0.02 |
40+
| | Data transfer fee | 50,000 GB * $0.02 | $1,000.00 |
41+
| | Price of network bandwidth (per GB) | Taken from sample prices | $0.02 |
42+
| | Network bandwidth fee | 50,000 GB * $0.02$ | $1,000.00 |
43+
| | Cost to replicate<br></br> | $1,000 + $1,000 | **$2,000** |
44+
| **Cost to read** | Number of read operations | 50,000 / 2 | 25,000 |
45+
| | Price a read operation on the hot tier | Taken from sample prices | $0.00440 |
46+
| | Cost of read operations<br></br> | 25,000 GB * $0.00440 | **$110.00** |
47+
| | Number of blobs downloaded from other regions | 25,000 * 75% | 1875 |
48+
| | Data transfer fee (downloads) | 1875 * $0.02 | $375.00 |
49+
| | Network bandwidth fee (downloads) | 1875 * $0.02 | $375.00 |
50+
| | Cost to transfer data out of region<br></br> | $375 + $375 | **$750.00** |
51+
| **Total cost** | | | **860.00** |
52+
53+
> [!TIP]
54+
> You can estimate the cost of these components in your environment by using [Azure pricing calculator](https://azure.microsoft.com/pricing/calculator/)
5955
6056
## See also
6157

0 commit comments

Comments
 (0)