liveBook · Manning

Tier transition

As explained in Microsoft Azure in Action

A tier transition is the movement of stored data from one storage access tier to another based on configured conditions.

A tier transition moves stored data between access tiers when configured conditions are met. Azure Storage lifecycle management automates this housekeeping, so rarely used blobs can become cheaper to store without manual sorting. section 9.5.1

A lifecycle rule can combine these actions:

  • Move a block blob from hot to cool after more than 30 days without modification. section 9.5.1
  • Move it from cool to archive after more than 90 days without modification. section 9.5.1
  • Delete it after 365 days, if deletion suits the retention policy. section 9.5.1
  • Let Azure move data back toward hot automatically when files are read or modified. section 9.5.1

Banning Books’ storage policy

A policy named TransitionHotToColdToArchive applies to block blobs, enables the lifecycle rule, and can be submitted with Azure CLI using az storage account management-policy create.

How Microsoft Azure in Action covers it

How deep it goes
Defines lifecycle rules with age thresholds, blob filters, deletion, and automatic movement back toward hot; it stops short of exhaustive configuration.
Examples
Demonstrates a Banning Books policy that transitions block blobs after 30 and 90 days and deletes them after 365 days.
What you can do after
Operate/configure Azure Storage lifecycle policies with JSON and Azure CLI.
How it connects
Connects Azure Storage lifecycle management with block blobs, hot, cool, and archive tiers, deletion, and access-cost trade-offs.
Cover of Microsoft Azure in Action
liveBookmanning.com
Read Microsoft Azure in Action on liveBook Get the book at manning.com

This explainer was generated by Manning's knowledge graph from the text of Microsoft Azure in Action. The section links point to the parts of the book it draws on.