If a data set needs to be readable, do not set a policy to move blobs to the archive tier. Lifecycle management doesn't affect system containers such as the $logs or $web containers. Lifecycle management policies are supported for block blobs and append blobs in general-purpose v2, premium block blob, and Blob Storage accounts. By moving data to the appropriate storage tier based on its age with lifecycle management policy rules, you can design the least expensive solution for your needs. Archive storage is the best tier option after the data ages over a month. Cool storage is most appropriate for occasional access. In this scenario, hot storage is best during the early stages. Beyond the first month, the data set is rarely accessed. Apply rules to containers or to a subset of blobs, using name prefixes or blob index tags as filters.Ĭonsider a scenario where data is frequently accessed during the early stages of the lifecycle, but only occasionally after two weeks.Define rules to be run once per day at the storage account level.Delete current versions of a blob, previous versions of a blob, or blob snapshots at the end of their lifecycles.Transition current versions of a blob, previous versions of a blob, or blob snapshots to a cooler storage tier if these objects haven't been accessed or modified for a period of time, to optimize for cost.Transition blobs from cool, or cold to hot immediately when they're accessed, to optimize for performance.With the lifecycle management policy, you can: This is separate from read transactions charges.
Life storage customer service update#
Each last access time update is charged as an "other transaction" at most once every 24 hours per object even if it's accessed 1000s of times in a day.
0 kommentar(er)
