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/archive-rehydrate-overview.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
@@ -5,7 +5,7 @@ services: storage
5
5
author: tamram
6
6
7
7
ms.author: tamram
8
-
ms.date: 03/28/2022
8
+
ms.date: 04/15/2022
9
9
ms.service: storage
10
10
ms.subservice: blobs
11
11
ms.topic: conceptual
@@ -61,17 +61,17 @@ To learn how to rehydrate a blob by copying it to an online tier, see [Rehydrate
61
61
> [!IMPORTANT]
62
62
> 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).
63
63
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.
65
65
66
66
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.
67
67
68
68
The following table shows the behavior of a blob copy operation, depending on the tiers of the source and destination blob.
|**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. |
|**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. |
0 commit comments