Skip to content

Commit cfa24f8

Browse files
committed
tweaks
1 parent 7e7e0eb commit cfa24f8

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

articles/storage/blobs/archive-rehydrate-overview.md

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

77
ms.author: tamram
8-
ms.date: 03/28/2022
8+
ms.date: 04/15/2022
99
ms.service: storage
1010
ms.subservice: blobs
1111
ms.topic: conceptual
@@ -61,17 +61,17 @@ To learn how to rehydrate a blob by copying it to an online tier, see [Rehydrate
6161
> [!IMPORTANT]
6262
> Do not delete the source blob until the rehydration has completed successfully. If the source blob is deleted, then the destination blob may not finish copying. You can handle the event that is raised when the copy operation completes to know when it is safe to delete the source blob. For more information, see [Handle an event on blob rehydration](#handle-an-event-on-blob-rehydration).
6363
64-
Copying an archived blob to an online destination tier is supported within the same storage account only for service versions prior to 2021-02-12. Beginning with service version 2021-02-12, you can copy an archived blob to a different storage account, as long as the destination account is in the same region as the source account.
64+
Rehydrating an archived blob by copying it to an online destination tier is supported within the same storage account only for service versions prior to 2021-02-12. Beginning with service version 2021-02-12, you can rehydrate an archived blob by copying it to a different storage account, as long as the destination account is in the same region as the source account. Rehydration across storage accounts enables you to segregate your production data from your backup data, by maintaining them in separate accounts. Isolating archived data in a separate account can also help to mitigate costs from unintentional rehydration.
6565

6666
The target blob for the copy operation must be in an online tier (Hot or Cool). You cannot copy an archived blob to a destination blob that is also in the Archive tier.
6767

6868
The following table shows the behavior of a blob copy operation, depending on the tiers of the source and destination blob.
6969

7070
| | **Hot tier source** | **Cool tier source** | **Archive tier source** |
7171
|--|--|--|--|
72-
| **Hot tier destination** | Supported | Supported | Supported within the same storage account. Supported across accounts in the same region with version 2021-02-12 and later. Requires blob rehydration. |
73-
| **Cool tier destination** | Supported | Supported | Supported within the same account. Supported across accounts in the same region with version 2021-02-12 and later. Requires blob rehydration. |
74-
| **Archive tier destination** | Supported | Supported | Unsupported |
72+
| **Hot tier destination** | Supported | Supported | Supported across accounts in the same region with version 2021-02-12 and later. Supported within the same storage account only for earlier versions. Requires blob rehydration. |
73+
| **Cool tier destination** | Supported | Supported | Supported across accounts in the same region with version 2021-02-12 and later. Supported within the same storage account only for earlier versions. Requires blob rehydration. |
74+
| **Archive tier destination** | Supported | Supported | Not supported |
7575

7676
## Change a blob's access tier to an online tier
7777

articles/storage/blobs/archive-rehydrate-to-online-tier.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: tamram
77

88
ms.service: storage
99
ms.topic: how-to
10-
ms.date: 04/14/2022
10+
ms.date: 04/15/2022
1111
ms.author: tamram
1212
ms.reviewer: fryu
1313
ms.custom: devx-track-azurepowershell

0 commit comments

Comments
 (0)