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/access-tiers-best-practices.md
+1-4Lines changed: 1 addition & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ description: Learn about best practice guidelines that help you use access tiers
5
5
author: normesta
6
6
7
7
ms.author: normesta
8
-
ms.date: 05/30/2023
8
+
ms.date: 08/10/2023
9
9
ms.service: storage
10
10
ms.topic: conceptual
11
11
---
@@ -25,9 +25,6 @@ To identify the most optimal access tier, try to estimate what percentage of the
25
25
26
26
To model and analyze the cost of using cool or cold versus archive storage, see [Archive versus cold and cool](archive-cost-estimation.md#archive-versus-cold-and-cool). You can apply similar modeling techniques to compare the cost of hot to cool, cold or archive.
27
27
28
-
> [!IMPORTANT]
29
-
> The cold tier is currently in PREVIEW. To learn more, see [Cold tier (preview)](access-tiers-overview.md#cold-tier-preview).
30
-
31
28
## Migrate data directly to the most cost-efficient access tiers
32
29
33
30
Choosing the most optimal tier up front can reduce costs. If you change the tier of a block blob that you've already uploaded, then you'll pay the cost of writing to the initial tier when you first upload the blob, and then pay the cost of writing to the desired tier. If you change tiers by using a lifecycle management policy, then that policy will require a day to take effect and a day to complete execution. You'll also incur the capacity cost of storing data in the initial tier prior to the tier change.
Copy file name to clipboardExpand all lines: articles/storage/blobs/access-tiers-online-manage.md
+2-13Lines changed: 2 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ description: Learn how to specify a blob's access tier when you upload it, or ho
5
5
author: normesta
6
6
7
7
ms.author: normesta
8
-
ms.date: 06/22/2023
8
+
ms.date: 08/10/2023
9
9
ms.service: storage
10
10
ms.topic: how-to
11
11
ms.reviewer: fryu
@@ -26,11 +26,6 @@ This article describes how to manage a blob in an online access tier. For more i
26
26
27
27
For more information about access tiers for blobs, see [Access tiers for blob data](access-tiers-overview.md).
28
28
29
-
> [!IMPORTANT]
30
-
> The cold tier is currently in PREVIEW and is available in the all public regions.
31
-
> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
32
-
> To enroll, see [Cold tier (preview)](access-tiers-overview.md#cold-tier-preview).
33
-
34
29
## Set the default access tier for a storage account
35
30
36
31
The default access tier setting for a general-purpose v2 storage account determines in which online tier a new blob is created by default. You can set the default access tier for a general-purpose v2 storage account at the time that you create the account or by updating an existing account's configuration.
@@ -118,9 +113,6 @@ To upload a blob or set of blobs to a specific tier from the Azure portal, follo
118
113
119
114
4. Expand the **Advanced** section, and set the **Access tier** to *Hot* or *Cool*.
120
115
121
-
> [!NOTE]
122
-
> The cold tier is in preview and appears as an option if the storage account is in a region that supports the preview.
123
-
124
116
5. Select the **Upload** button.
125
117
126
118
:::image type="content" source="media/access-tiers-online-manage/upload-blob-to-online-tier-portal.png" alt-text="Screenshot showing how to upload blobs to an online tier in the Azure portal.":::
@@ -329,7 +321,7 @@ az storage blob set-tier \
329
321
330
322
#### [AzCopy](#tab/azcopy)
331
323
332
-
To change a blob's tier to a cooler tier, use the [azcopy set-properties](..\common\storage-ref-azcopy-set-properties.md) command and set the `-block-blob-tier` parameter.
324
+
To change a blob's tier to a cooler tier, use the [azcopy set-properties](..\common\storage-ref-azcopy-set-properties.md) command and set the `-block-blob-tier` parameter.
333
325
334
326
> [!IMPORTANT]
335
327
> Using AzCopy to change a blob's access tier is currently in PREVIEW.
@@ -342,9 +334,6 @@ To change a blob's tier to a cooler tier, use the [azcopy set-properties](..\com
> Setting the `--block-blob-tier` parameter to `cold` is not yet supported. If you want to change a blob's tier to the `cold` tier, [enroll](https://forms.office.com/r/788B1gr3Nq) in the cold tier preview, and then change the blob's tier to cold by using the Azure portal, PowerShell, or the Azure CLI.
347
-
348
337
To change the access tier for all blobs in a virtual directory, refer to the virtual directory name instead of the blob name, and then append `--recursive=true` to the command.
Copy file name to clipboardExpand all lines: articles/storage/blobs/access-tiers-overview.md
+4-13Lines changed: 4 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ description: Azure storage offers different access tiers so that you can store y
5
5
author: normesta
6
6
7
7
ms.author: normesta
8
-
ms.date: 07/13/2023
8
+
ms.date: 08/10/2023
9
9
ms.service: storage
10
10
ms.topic: conceptual
11
11
ms.reviewer: fryu
@@ -20,11 +20,6 @@ Data stored in the cloud grows at an exponential pace. To manage costs for your
20
20
-**Cold tier** - An online tier optimized for storing data that is infrequently accessed or modified. Data in the cold tier should be stored for a minimum of **90** days. The cold tier has lower storage costs and higher access costs compared to the cool tier.
21
21
-**Archive tier** - An offline tier optimized for storing data that is rarely accessed, and that has flexible latency requirements, on the order of hours. Data in the archive tier should be stored for a minimum of 180 days.
22
22
23
-
> [!IMPORTANT]
24
-
> The cold tier is currently in PREVIEW and is available in all public regions.
25
-
> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
26
-
> To enroll, see [Cold tier (preview)](#cold-tier-preview).
27
-
28
23
Azure storage capacity limits are set at the account level, rather than according to access tier. You can choose to maximize your capacity usage in one tier, or to distribute capacity across two or more tiers.
29
24
30
25
> [!NOTE]
@@ -136,7 +131,7 @@ Blob storage lifecycle management offers a rule-based policy that you can use to
136
131
137
132
The following table summarizes the features of the hot, cool, cold, and archive access tiers.
@@ -198,13 +193,9 @@ The following table summarizes how tier changes are billed.
198
193
199
194
Changing the access tier for a blob when versioning is enabled, or if the blob has snapshots, might result in more charges. For information about blobs with versioning enabled, see [Pricing and billing](versioning-overview.md#pricing-and-billing) in the blob versioning documentation. For information about blobs with snapshots, see [Pricing and billing](snapshots-overview.md#pricing-and-billing) in the blob snapshots documentation.
200
195
201
-
## Cold tier (preview)
202
-
203
-
The cold tier is currently in PREVIEW and is available in all public regions except Poland Central and Qatar Central.
204
-
205
-
### Enrolling in the preview
196
+
## Cold tier
206
197
207
-
You can validate cold tier on a general-purpose v2 storage account from any subscription in Azure public cloud. It's still recommended to share your scenario in the [preview form](https://forms.office.com/r/788B1gr3Nq).
198
+
The cold tier is now generally available in all public and Azure Government regions except Poland Central and Qatar Central.
Copy file name to clipboardExpand all lines: articles/storage/blobs/archive-cost-estimation.md
+1-5Lines changed: 1 addition & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ description: Learn how to calculate the cost of storing and maintaining data in
5
5
author: normesta
6
6
7
7
ms.author: normesta
8
-
ms.date: 05/30/2023
8
+
ms.date: 08/10/2023
9
9
ms.service: storage
10
10
ms.topic: conceptual
11
11
---
@@ -287,10 +287,6 @@ This scenario assumes a monthly ingest of 200,000 files totaling 10,240 GB in si
287
287
Archive storage is the lowest cost tier. However, it can take up to 15 hours to rehydrate 10 GiB files. To learn more, see [Blob rehydration from the Archive tier](archive-rehydrate-overview.md). The archive tier might not be the best fit if your workloads must read data quickly. The cool tier offers a near real-time read latency with a lower price than that the hot tier. Understanding your access requirements will help you to choose between the cool, cold, and archive tiers.
288
288
289
289
The following table compares the cost of archive storage with the cost of cool and cold storage by using the [Sample prices](#sample-prices) that appear in this article. This scenario assumes a monthly ingest of 200,000 files totaling 10,240 GB in size to archive. It also assumes 1 read each month about 10% of stored capacity (1024 GB), and 10% of total transactions (20,000).
290
-
291
-
> [!IMPORTANT]
292
-
> The cold tier is currently in PREVIEW. To learn more, see [Cold tier (preview)](access-tiers-overview.md#cold-tier-preview).
Copy file name to clipboardExpand all lines: articles/storage/blobs/lifecycle-management-overview.md
+1-6Lines changed: 1 addition & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ description: Use Azure Storage lifecycle management policies to create automated
5
5
author: normesta
6
6
7
7
ms.author: normesta
8
-
ms.date: 08/03/2023
8
+
ms.date: 08/10/2023
9
9
ms.service: azure-storage
10
10
ms.subservice: storage-common-concepts
11
11
ms.topic: conceptual
@@ -28,11 +28,6 @@ With the lifecycle management policy, you can:
28
28
- Define rules to be run once per day at the storage account level.
29
29
- Apply rules to containers or to a subset of blobs, using name prefixes or [blob index tags](storage-manage-find-blobs.md) as filters.
30
30
31
-
> [!IMPORTANT]
32
-
> The cold tier is currently in PREVIEW and is available in all public regions.
33
-
> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
34
-
> To enroll, see [Cold tier (preview)](access-tiers-overview.md#cold-tier-preview).
35
-
36
31
Consider a scenario where data is frequently accessed during the early stages of the lifecycle, but only occasionally after two weeks. Beyond the first month, the data set is rarely accessed. In this scenario, hot storage is best during the early stages. Cool storage is most appropriate for occasional access. Archive storage is the best tier option after the data ages over a month. By moving data to the appropriate storage tier based on its age with lifecycle management policy rules, you can design the least expensive solution for your needs.
37
32
38
33
Lifecycle management policies are supported for block blobs and append blobs in general-purpose v2, premium block blob, and Blob Storage accounts. Lifecycle management doesn't affect system containers such as the `$logs` or `$web` containers.
0 commit comments