Merge pull request #193167 from tamram/tamram22-0322

LJSpiller · web-flow · commit 656a13a8e9ed · 2022-04-15T18:24:03.000-04:00
cross-account copy for rehydrating from archive tier
diff --git a/articles/storage/blobs/archive-rehydrate-overview.md b/articles/storage/blobs/archive-rehydrate-overview.md
@@ -5,7 +5,7 @@ services: storage
 author: tamram
 
 ms.author: tamram
-ms.date: 03/01/2022
+ms.date: 04/15/2022
 ms.service: storage
 ms.subservice: blobs
 ms.topic: conceptual
@@ -54,22 +54,24 @@ Microsoft recommends performing a copy operation in most scenarios where you nee
 - A copy operation avoids the early deletion fee that is assessed if you change the tier of a blob from the Archive tier before the required 180-day period elapses. For more information, see [Archive access tier](access-tiers-overview.md#archive-access-tier).
 - If there is a lifecycle management policy in effect for the storage account, then rehydrating a blob with [Set Blob Tier](/rest/api/storageservices/set-blob-tier) can result in a scenario where the lifecycle policy moves the blob back to the Archive tier after rehydration because the last modified time is beyond the threshold set for the policy. A copy operation leaves the source blob in the Archive tier and creates a new blob with a different name and a new last modified time, so there is no risk that the rehydrated blob will be moved back to the Archive tier by the lifecycle policy.
 
-Copying a blob from the Archive tier can take hours to complete depending on the rehydration priority selected. Behind the scenes, a blob copy operation reads your archived source blob to create a new online blob in the selected destination tier. The new blob may be visible when you list the blobs in the parent container before the rehydration operation is complete, but its tier will be set to Archive, The data is not available until the read operation from the source blob in the Archive tier is complete and the blob's contents have been written to the new destination blob in an online tier. The new blob is an independent copy, so modifying or deleting it does not affect the source blob in the Archive tier.
+Copying a blob from the Archive tier can take hours to complete depending on the rehydration priority selected. Behind the scenes, a blob copy operation reads your archived source blob to create a new online blob in the selected destination tier. The new blob may be visible when you list the blobs in the parent container before the rehydration operation is complete, but its tier will be set to Archive. The data is not available until the read operation from the source blob in the Archive tier is complete and the blob's contents have been written to the new destination blob in an online tier. The new blob is an independent copy, so modifying or deleting it does not affect the source blob in the Archive tier.
 
 To learn how to rehydrate a blob by copying it to an online tier, see [Rehydrate a blob with a copy operation](archive-rehydrate-to-online-tier.md#rehydrate-a-blob-with-a-copy-operation).
 
 > [!IMPORTANT]
 > 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).
 
-Copying an archived blob to an online destination tier is supported within the same storage account only. You cannot copy an archived blob to a destination blob that is also in the Archive tier.
+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.
+
+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.
 
 The following table shows the behavior of a blob copy operation, depending on the tiers of the source and destination blob.
 
 |  | **Hot tier source** | **Cool tier source** | **Archive tier source** |
 |--|--|--|--|
-| **Hot tier destination** | Supported | Supported | Supported within the same account. Requires blob rehydration. |
-| **Cool tier destination** | Supported | Supported | Supported within the same account. Requires blob rehydration. |
-| **Archive tier destination** | Supported | Supported | Unsupported |
+| **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. |
+| **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. |
+| **Archive tier destination** | Supported | Supported | Not supported |
 
 ## Change a blob's access tier to an online tier
 
diff --git a/articles/storage/blobs/archive-rehydrate-to-online-tier.md b/articles/storage/blobs/archive-rehydrate-to-online-tier.md
@@ -7,7 +7,7 @@ author: tamram
 
 ms.service: storage
 ms.topic: how-to
-ms.date: 03/01/2022
+ms.date: 04/15/2022
 ms.author: tamram
 ms.reviewer: fryu
 ms.custom: devx-track-azurepowershell
@@ -31,15 +31,19 @@ For more information about rehydrating a blob, see [Blob rehydration from the Ar
 
 To rehydrate a blob from the Archive tier by copying it to an online tier, use PowerShell, Azure CLI, or one of the Azure Storage client libraries. Keep in mind that when you copy an archived blob to an online tier, the source and destination blobs must have different names.
 
+Copying an archived blob to an online destination tier is supported within the same storage account. 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.
+
 After the copy operation is complete, the destination blob appears in the Archive tier. The destination blob is then rehydrated to the online tier that you specified in the copy operation. When the destination blob is fully rehydrated, it becomes available in the new online tier.
 
-The following examples show how to copy an archived blob with PowerShell or Azure CLI.
+### Rehydrate a blob to the same storage account
 
-### [Portal](#tab/azure-portal)
+The following examples show how to copy an archived blob to a blob in the Hot tier in the same storage account.
+
+#### [Portal](#tab/azure-portal)
 
 N/A
 
-### [PowerShell](#tab/azure-powershell)
+#### [PowerShell](#tab/azure-powershell)
 
 To copy an archived blob to an online tier with PowerShell, call the [Start-AzStorageBlobCopy](/powershell/module/az.storage/start-azstorageblobcopy) command and specify the target tier and the rehydration priority. Remember to replace placeholders in angle brackets with your own values:
 
@@ -67,7 +71,7 @@ Start-AzStorageBlobCopy -SrcContainer $srcContainerName `
     -Context $ctx
 ```
 
-### [Azure CLI](#tab/azure-cli)
+#### [Azure CLI](#tab/azure-cli)
 
 To copy an archived blob to an online tier with Azure CLI, call the [az storage blob copy start](/cli/azure/storage/blob/copy#az-storage-blob-copy-start) command and specify the target tier and the rehydration priority. Remember to replace placeholders in angle brackets with your own values:
 
@@ -85,6 +89,87 @@ az storage blob copy start \
 
 ---
 
+### Rehydrate a blob to a different storage account in the same region
+
+The following examples show how to copy an archived blob to a blob in the Hot tier in a different storage account.
+
+#### [Portal](#tab/azure-portal)
+
+N/A
+
+#### [PowerShell](#tab/azure-powershell)
+
+To copy an archived blob to a blob in an online tier in a different storage account with PowerShell, make sure you have installed the [Az.Storage](https://www.powershellgallery.com/packages/Az.Storage/) module, version 4.4.0 or higher. Next, call the [Start-AzStorageBlobCopy](/powershell/module/az.storage/start-azstorageblobcopy) command and specify the target online tier and the rehydration priority. You must specify a shared access signature (SAS) with read permissions for the archived source blob.
+
+The following example shows how to copy an archived blob to the Hot tier in a different storage account. Remember to replace placeholders in angle brackets with your own values:
+
+```powershell
+$rgName = "<resource-group>"
+$srcAccount = "<source-account>"
+$destAccount = "<dest-account>"
+$srcContainer = "<source-container>"
+$destContainer = "<dest-container>" 
+$srcBlob = "<source-blob>"
+$destBlob = "<destination-blob>"
+
+# Get the destination account context
+$destCtx = New-AzStorageContext -StorageAccountName $destAccount -UseConnectedAccount
+
+# Get the source account context
+$srcCtx = New-AzStorageContext -StorageAccountName $srcAccount -UseConnectedAccount
+
+# Get the SAS URI for the source blob
+$srcBlobUri = New-AzStorageBlobSASToken -Container $srcContainer `
+    -Blob $srcBlob `
+    -Permission rwd `
+    -ExpiryTime (Get-Date).AddDays(1) `
+    -FullUri `
+    -Context $srcCtx
+
+# Start the cross-account copy operation
+Start-AzStorageBlobCopy -AbsoluteUri $srcBlobUri `
+    -DestContainer $destContainer `
+    -DestBlob $destBlob `
+    -DestContext $destCtx `
+    -StandardBlobTier Hot `
+    -RehydratePriority Standard
+```
+
+#### [Azure CLI](#tab/azure-cli)
+
+To copy an archived blob to a blob in an online tier in a different storage account with the Azure CLI, make sure you have installed version 2.35.0 or higher. Next, call the [az storage blob copy start](/cli/azure/storage/blob/copy#az-storage-blob-copy-start) command and specify the target online tier and the rehydration priority. You must specify a shared access signature (SAS) with read permissions for the archived source blob.
+
+The following example shows how to copy an archived blob to the Hot tier in a different storage account. Remember to replace placeholders in angle brackets with your own values:
+
+```azurecli
+# Specify the expiry interval
+end=`date -u -d "1 day" '+%Y-%m-%dT%H:%MZ'`
+
+# Get a SAS for the source blob
+srcBlobUri=$(az storage blob generate-sas \
+            --account-name <source-account> \ 
+            --container <source-container> \
+            --name <archived-source-blob> \
+            --permissions rwd \
+            --expiry $end \
+            --https-only \
+            --full-uri \
+            --as-user \
+            --auth-mode login | tr -d '"')
+
+# Copy to the destination blob in the Hot tier
+az storage blob copy start \
+    --source-uri $srcBlobUri \
+    --account-name <dest-account> \
+    --destination-container <dest-container> \
+    --destination-blob <dest-blob> \
+    --tier Hot \
+    --rehydrate-priority Standard \
+    --auth-mode login
+```
+
+---
+
 ## Rehydrate a blob by changing its tier
 
 To rehydrate a blob by changing its tier from Archive to Hot or Cool, use the Azure portal, PowerShell, or Azure CLI.
