리하이드레이션이 최대 15시간 걸리는 이유?

Question

https://learn.microsoft.com/ko-kr/azure/storage/blobs/archive-blob?tabs=azure-portal

링크에서 리하이드레이션이 최대 15시간 걸린다고 되어있는데

어떤 근거로 계산됬는지 궁금합니다.

방식이 있는것인지?

설명해주세요

Answer 1

@MNYE Welcome to Microsoft Q&A Forum, Thank you for posting your here!

We cannot completely understand your question as this is an English global support. It would be helpful, if you can translate your question in English. Or you can consider support in other languages from here: https://azure.microsoft.com/support/options/

Refer the FAQ here: For which languages does Microsoft provide support?

After translating your question, this is what I understood: How rehydration calculation is calculated?

Rehydrating a blob can take up to 15 hours, depending on the rehydration priority setting. If you set the rehydration priority to High, rehydration may complete in under one hour for blobs that are less than 10 GB in size. However, a high-priority rehydration incurs a greater cost. For more information, see Overview of blob rehydration from the Archive tier.

You can only rehydrate first 10 GB in 15 hours with standard retrieval. For the rest of data, the retrieval speed is 60 MBps to 100 MBps. Daily retrieval speed would be 5 TiB to 8 TiB. However, there are many factors that may affect rehydration performance, including file size distribution, how files are archived over past time windows, etc.

When you rehydrate a blob, you can set the priority for the rehydration operation via the optional x-ms-rehydrate-priority header on a Set Blob Tier or Copy Blob operation. Rehydration priority options include:

• Standard priority: The rehydration request will be processed in the order it was received and may take up to 15 hours to complete for objects under 10 GB in size.
• High priority: The rehydration request will be prioritized over standard priority requests and may complete in less than one hour for objects under 10 GB in size.

To check the rehydration priority while the rehydration operation is underway, call Get Blob Properties to return the value of the x-ms-rehydrate-priority header. The rehydration priority property returns either Standard or High.

Standard priority is the default rehydration option. A high-priority rehydration is faster, but also costs more than a standard-priority rehydration. A high-priority rehydration may take longer than one hour, depending on blob size and current demand. Microsoft recommends reserving high-priority rehydration for use in emergency data restoration situations.

While a standard-priority rehydration operation is pending, you can update the rehydration priority setting for a blob to High to rehydrate that blob more quickly. For example, if you're rehydrating a large number of blobs in bulk, you can specify Standard priority for all blobs for the initial operation, then increase the priority to High for any individual blobs that need to be brought online more quickly, up to the limit of 10 GiB per hour.

The rehydration priority setting can't be lowered from High to Standard for a pending operation. Keep in mind that updating the rehydration priority setting may have a billing impact.

To learn how to set and update the rehydration priority setting, see Rehydrate an archived blob to an online tier.

For more information on pricing differences between standard-priority and high-priority rehydration requests, see Pricing for Azure Blob Storage.

Please let us know if you have any further queries. I’m happy to assist you further.   

---

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.