Lifecycle Management

 

Azure Blob Storage lifecycle management offers a rich, rule-based policy which you can use to transition your data to the best access tier and to expire data at the end of its lifecycle.

Lifecycle management policy helps you:

• Transition blobs to a cooler storage tier such as hot to cool, hot to archive, or cool to archive in order to optimize for performance and cost
• Delete blobs at the end of their lifecycles
• Define up to 100 rules
• Run rules automatically once a day
• Apply rules to containers or specific subset of blobs, up to 10 prefixes per rule
• To learn more visit documentation, “Managing the Azure Blob storage Lifecycle.”

For example, We have a data set that is accessed very frequently during the first month and it is needed only occasionally for the next two months and then it is rarely accessed afterwards, and is required to be expired after 10 years. 

In this scenario, hot storage is the best tier to use initially, cool storage is appropriate for occasional access, and archive storage is the best tier after several months and before it is deleted.

• Tier blobs to cool storage 30 days after last modification
• Tier blobs to archive storage 90 days after last modification
• Delete blobs 3,650 days (Ten years) after last modification
• Delete blob snapshots 90 days after snapshot creation