Saving blob in Archive Tier

HitenBhavsar-MSFT 381 Reputation points Microsoft Employee
2020-05-08T16:20:21.57+00:00

I understand that I can only save Blob's in hot or cold tier. Later on I can switch the tier to Archive. Does that mean I pay for the write operation twice. Once to write to Hot/Cold, then again to archive (while switching the tier back to archive)?

[Note: As we migrate from MSDN, this question has been posted by an Azure Cloud Engineer as a frequently asked question.]

Reference:

Only the hot and cool access tiers can be set at the account level.

When a blob is moved to a cooler tier (hot->cool, hot->archive, or cool->archive), the operation is billed as a write operation to the destination tier, where the write operation (per 10,000) and data write (per GB) charges of the destination tier apply.

Azure
Azure
A cloud computing platform and infrastructure for building, deploying and managing applications and services through a worldwide network of Microsoft-managed datacenters.
1,069 questions
0 comments No comments
{count} votes

Accepted answer
  1. Sumarigo-MSFT 45,406 Reputation points Microsoft Employee
    2020-05-08T16:22:48.083+00:00

    That is correct, the initial save of blobs into storage would be a write operation in cool or hot, then switching to archive would be another operation:

    When a blob is moved to a cooler tier (hot->cool, hot->archive, or cool->archive), the operation is billed as a write operation to the destination tier, where the write operation (per 10,000) and data write (per GB) charges of the destination tier apply.

    When a blob is moved to a warmer tier (archive->cool, archive->hot, or cool->hot), the operation is billed as a read from the source tier, where the read operation (per 10,000) and data retrieval (per GB) charges of the source tier apply. The following table summarizes how tier changes are billed.

    Source: MSDN

    0 comments No comments

0 additional answers

Sort by: Most helpful