In an Azure Storage Account, how are lifecycle management policy actions prioritized on a blob?

Priyanka Chaudhuri 105 Reputation points
2023-08-12T21:56:20.8433333+00:00

In this link, it is stated that "If you define more than one action on the same blob, lifecycle management applies the least expensive action to the blob".

How does Azure prioritize actions when -

  1. How is an action decided to be cheaper on a blob? Does Azure take into account the blob's current tier?
  2. tierToArchive action is set if daysAfterModificationGreaterThan = 90 and delete action is set if daysAfterModificationGreaterThan = 100. (As per the link, delete is a cheaper action compared to moving tier, however tierToArchive action condition is met 10 days before delete action's condition)
  3. Does Azure prioritize the lifecycle policy actions differently for base blob, previous version and snapshots?
  4. Why does Azure not support moving archive tier to online tier using lifecycle management policy?
  5. Why is archive tier not supported in storage accounts with ZRS, GZRS or RA-GZRS?
Azure Storage Explorer
Azure Storage Explorer
An Azure tool that is used to manage cloud storage resources on Windows, macOS, and Linux.
240 questions
Azure Storage Accounts
Azure Storage Accounts
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
2,871 questions
Accepted answer
  1. ChakaravarthiRangarajanBhargavi-1820 715 Reputation points
    2023-09-10T08:34:03.3533333+00:00

    Hi @Priyanka Chaudhuri

    Azure Blob Storage applies the least expensive action to a blob if you define more than one action for the same blob. This means that Azure considers the cost of the action when multiple actions are defined for the same blob. It provides flexibility in specifying actions like moving blobs to different storage tiers or deleting them based on conditions you set. Once a condition is met for a blob, the corresponding action is executed, and no further actions for that blob are considered. Azure considers the cost of actions when deciding which action to execute. Typically, deleting a blob is cheaper than moving it to a different storage tier. Azure will choose the cheaper action if both conditions are met. In your example, if daysAfterModificationGreaterThan is 100 for a blob, it will be deleted instead of being moved to archive tier if daysAfterModificationGreaterThan is 90. This is because deletion is more cost-effective. You will not be able to move the data from archive tier to hot or cool in online. Azure Archive Storage is designed for long-term data retention and is not intended for scenarios requiring high availability or frequent access. These replication options provide high availability, which may not align with the intended use of the Archive tier.

    Regards,

    Chakravarthi Rangarajan Bhargavi

    -Please kindly accept the answer and vote 'Yes' if you feel helpful to support the community, thanks a lot.

    0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest