从存档层解冻 Blob 数据Rehydrate blob data from the archive tier

当 Blob 位于存档访问层时,它被视为脱机状态,无法对其进行读取或修改。While a blob is in the archive access tier, it's considered offline and can't be read or modified. Blob 元数据保持联机和可用状态,你可以列出 Blob 及其属性。The blob metadata remains online and available, allowing you to list the blob and its properties. 只能读取和修改联机层(例如热层或冷层)中的 Blob 数据。Reading and modifying blob data is only available with online tiers such as hot or cool. 可使用两个选项来检索和访问存档访问层中存储的数据。There are two options to retrieve and access data stored in the archive access tier.

  1. 将存档的 Blob 解冻到联机层 - 使用设置 Blob 层操作将存档的 Blob 解冻至热层或冷层。Rehydrate an archived blob to an online tier - Rehydrate an archive blob to hot or cool by changing its tier using the Set Blob Tier operation.
  2. 将存档的 Blob 复制到联机层 - 使用复制 Blob 操作创建已存档 Blob 的新副本。Copy an archived blob to an online tier - Create a new copy of an archive blob by using the Copy Blob operation. 指定不同的 Blob 名称,以及目标热层或冷层。Specify a different blob name and a destination tier of hot or cool.

有关层的详细信息,请参阅 Azure Blob 存储:热、冷和存档访问层For more information on tiers, see Azure Blob storage: hot, cool, and archive access tiers.

将存档的 Blob 解冻到联机层Rehydrate an archived blob to an online tier

若要读取存档存储中的数据,必须先将 Blob 的层更改为热层或冷层。To read data in archive storage, you must first change the tier of the blob to hot or cool. 此过程称为解冻,可能需要多个小时才能完成。This process is known as rehydration and can take hours to complete. 建议使用较大的 Blob 大小,以优化解冻性能。We recommend large blob sizes for optimal rehydration performance. 同时解冻多个小型 Blob 可能导致该时间延长。Rehydrating several small blobs concurrently may add additional time. 目前有两种解冻优先级:“高”和“标准”,可以在设置 Blob 层复制 Blob 操作中通过可选的 x-ms-rehydrate-priority 属性进行设置**。There are currently two rehydrate priorities, High and Standard, which can be set via the optional x-ms-rehydrate-priority property on a Set Blob Tier or Copy Blob operation.

  • 标准优先级:解冻请求将按其接收顺序处理,最长可能需要 15 个小时。Standard priority: The rehydration request will be processed in the order it was received and may take up to 15 hours.
  • 高优先级:解冻请求优先于标准请求,对于大小小于 10 GB 的对象,可在 1 小时内完成。High priority: The rehydration request will be prioritized over Standard requests and may finish in under 1 hour for objects under ten GB in size.


标准优先级是存档的默认解冻选项。Standard priority is the default rehydration option for archive. 高优先级是更快的选项,其费用高于标准优先级解冻,通常保留用于紧急数据还原。High priority is a faster option that will cost more than Standard priority rehydration and is usually reserved for use in emergency data restoration situations.

高优先级请求可能需要花费 1 小时以上,具体取决于 Blob 大小和当前需求。High priority may take longer than 1 hour, depending on blob size and current demand. 保证高优先级请求优先于标准优先级请求。High priority requests are guaranteed to be prioritized over Standard priority requests.

发起解冻请求后,将无法取消。Once a rehydration request is initiated, it cannot be canceled. 在解冻过程中,x-ms-access-tier blob 属性将继续显示为存档,直到解冻过程进展到联机层**。During the rehydration process, the x-ms-access-tier blob property will continue to show as archive until rehydration is completed to an online tier. 要确认解冻状态和进度,可以调用获取 Blob 属性以查看 x-ms-archive-status 和 x-ms-rehydrate-priority blob 属性** **。To confirm rehydration status and progress, you may call Get Blob Properties to check the x-ms-archive-status and the x-ms-rehydrate-priority blob properties. 存档状态可显示为“rehydrate-pending-to-hot”或“rehydrate-pending-to-cool”,具体取决于解除冻结目标层。The archive status can read "rehydrate-pending-to-hot" or "rehydrate-pending-to-cool" depending on the rehydrate destination tier. 解冻优先级将指示“高”或“标准”的速度。The rehydrate priority will indicate the speed of "High" or "Standard". 解冻完成后,将删除存档状态和解冻优先级属性,并更新访问层 blob 属性以反映所选的热存储层或冷存储层。Upon completion, the archive status and rehydrate priority properties are removed, and the access tier blob property will update to reflect the selected hot or cool tier.

将存档的 Blob 复制到联机层Copy an archived blob to an online tier

如果你不想要解冻存档的 Blob,可以选择执行复制 Blob 操作。If you don't want to rehydrate your archive blob, you can choose to do a Copy Blob operation. 原始 Blob 在存档中保持未修改状态,同时会在热层或冷层中联机创建新的 Blob 供你使用。Your original blob will remain unmodified in archive while a new blob is created in the online hot or cool tier for you to work on. 在“复制 Blob”操作中,还可以将可选的 x-ms-rehydrate-priority 属性置为“标准”或“高”,以指定要在哪个优先级创建你的 Blob 副本。In the Copy Blob operation, you may also set the optional x-ms-rehydrate-priority property to Standard or High to specify the priority at which you want your blob copy created.

从存档中复制 Blob 可能需要数小时才能完成,具体取决于所选解冻优先级。Copying a blob from archive can take hours to complete depending on the rehydrate priority selected. 在幕后,“复制 Blob”操作会读取存档源 Blob,以便在所选目标层中创建新的联机 Blob。Behind the scenes, the Copy Blob operation reads your archive source blob to create a new online blob in the selected destination tier. 列出 Blob 时,新 Blob 也许可见,但数据并不可用,直到从源存档 Blob 进行读取的操作完成并将数据写入到新的联机目标 Blob 为止。The new blob may be visible when you list blobs but the data is not available until the read from the source archive blob is complete and data is written to the new online destination blob. 新 Blob 充当独立的副本,对它进行的任何修改或删除操作不会影响源存档 Blob。The new blob is as an independent copy and any modification or deletion to it does not affect the source archive blob.


在目标上成功完成复制之前,请不要删除源 Blob。Do not delete the the source blob until the copy is completed successfully at the destination. 如果删除源 Blob,则目标 Blob 可能无法完成复制并且将为空。If the source blob is deleted then the destination blob may not complete copying and will be empty. 可以查看 x-ms-copy-status 来确定复制操作的状态。You may check the x-ms-copy-status to determine the state of the copy operation.

只能将存档 Blob 复制到同一存储帐户中的联机目标层。Archive blobs can only be copied to online destination tiers within the same storage account. 不支持将存档 Blob 复制到另一个存档 Blob。Copying an archive blob to another archive blob is not supported. 下表说明了 CopyBlob 的功能。The following table indicates CopyBlob's capabilities.

热层源Hot tier source 冷层源Cool tier source 存档层源Archive tier source
热层目标Hot tier destination 支持Supported 支持Supported 在同一帐户中受支持;待解除冻结Supported within the same account; pending rehydrate
冷层目标Cool tier destination 支持Supported 支持Supported 在同一帐户中受支持;待解除冻结Supported within the same account; pending rehydrate
存档层目标Archive tier destination 支持Supported 支持Supported 不支持Unsupported

定价和计费Pricing and billing

将存档中的 Blob 解冻到热层或冷层会产生读取操作和数据检索费用。Rehydrating blobs out of archive into hot or cool tiers are charged as read operations and data retrieval. 与标准优先级相比,使用高优先级时操作和数据检索的成本更高。Using High priority has higher operation and data retrieval costs compared to standard priority. 高优先级解冻在账单上单独显示费用细目。High priority rehydration shows up as a separate line item on your bill. 如果返回若干 GB 存档 Blob 的高优先级请求花费了 5 小时以上,则不会按照高优先级检索费率向你收费。If a high priority request to return an archive blob of a few gigabytes takes over 5 hours, you won't be charged the high priority retrieval rate. 不过,标准检索费率仍适用,因为解冻的优先级高于其他请求。However, standard retrieval rates still apply as the rehydration was prioritized over other requests.

将存档中的 Blob 复制到热层或冷层会产生读取操作和数据检索费用。Copying blobs from archive into hot or cool tiers are charged as read operations and data retrieval. 创建新的 Blob 副本会产生写入操作费用。A write operation is charged for the creation of the new blob copy. 复制到联机 Blob 时,不会产生提前删除费,因为源 Blob 在存档层中保持未修改状态。Early deletion fees don't apply when you copy to an online blob because the source blob remains unmodified in the archive tier. 高优先级检索费用适用(如果已选中)。High priority retrieval charges do apply if selected.

存档层中的 Blob 应至少存储 180 天。Blobs in the archive tier should be stored for a minimum of 180 days. 在 180 天之前删除或解冻存档的 Blob 会导致提前删除费。Deleting or rehydrating archived blobs before 180 days will incur early deletion fees.


有关块 Blob 和数据解冻的定价详细信息,请参阅 Azure 存储定价For more information about pricing for block blobs and data rehydration, see Azure Storage Pricing. 有关出站数据传输费的详细信息,请参阅数据传输定价详细信息For more information on outbound data transfer charges, see Data Transfers Pricing Details.

快速入门方案Quickstart scenarios

将存档 Blob 解冻到联机层Rehydrate an archive blob to an online tier

  1. 登录到 Azure 门户Sign in to the Azure portal.

  2. 在 Azure 门户中,搜索并选择“所有资源”。In the Azure portal, search for and select All Resources.

  3. 选择存储帐户。Select your storage account.

  4. 选择容器,然后选择 Blob。Select your container and then select your blob.

  5. 在“Blob 属性”中选择“更改层”。 In the Blob properties, select Change tier.

  6. 选择“热”或“冷”访问层。 Select the Hot or Cool access tier.

  7. 选择“标准”或“高”作为“解除冻结优先级”。 Select a Rehydrate Priority of Standard or High.

  8. 选择底部的“保存”。Select Save at the bottom.

更改存储帐户层 检查解除冻结状态Change storage account tier Check rehydrate status

将存档 Blob 复制到联机层的新 BlobCopy an archive blob to a new blob with an online tier

可以使用以下 PowerShell 脚本将存档 Blob 复制到同一存储帐户中的新 Blob。The following PowerShell script can be used to copy an archive blob to a new blob within the same storage account. 必须使用资源组名称初始化 $rgName 变量。The $rgName variable must be initialized with your resource group name. 必须使用你的存储帐户名初始化 $accountName 变量。The $accountName variable must be initialized with your storage account name. 必须使用容器名称初始化 $srcContainerName$destContainerName 变量。The $srcContainerName and $destContainerName variables must be initialized with your container names. 必须使用 Blob 名称初始化 $srcBlobName$destBlobName 变量。The $srcBlobName and $destBlobName variables must be initialized with your blob names.

#Initialize the following with your resource group, storage account, container, and blob names
$rgName = ""
$accountName = ""
$srcContainerName = ""
$destContainerName = ""
$srcBlobName = ""
$destBlobName = ""

#Select the storage account and get the context
$storageAccount =Get-AzStorageAccount -ResourceGroupName $rgName -Name $accountName
$ctx = $storageAccount.Context

#Copy source blob to a new destination blob with access tier hot using standard rehydrate priority
Start-AzStorageBlobCopy -SrcContainer $srcContainerName -SrcBlob $srcBlobName -DestContainer $destContainerName -DestBlob $destBlobName -StandardBlobTier Hot -RehydratePriority Standard -Context $ctx

后续步骤Next Steps