Azure Storage Account | Blob Hot vs Cool vs Archive | Optimize Costs with Azure
6.1 هزار بار بازدید -
3 سال پیش
-
In this demo I have
In this demo I have explained different access tiers of Azure storage account. i.e. Blob Hot vs Cool vs Archive tiers. Also about Blob Life Cycle Management. I have shown changing the tiers at storage account level - before creation and after creation also at the blob level. see below for detailed explanation about Blob Hot vs cool vs archive tiers. Also I have shown moving the tiers automatically based on specific criteria using blob life cycle management. Below are the definitions of Blob Access tiers.
----------------------------------------
Hot tier - An online tier optimized for storing data that is accessed or modified frequently. The hot tier has the highest storage costs, but the lowest access costs.
Cool tier - An online tier optimized for storing data that is infrequently accessed or modified. Data in the cool tier should be stored for a minimum of 30 days. The cool tier has lower storage costs and higher access costs compared to the hot tier.
Archive tier - An offline tier optimized for storing data that is rarely accessed, and that has flexible latency requirements, on the order of hours. Data in the archive tier should be stored for a minimum of 180 days.
-------------------------------------------
I have also shown managing the tiers using .net core console application where the .net core console application moved the blobs from Hot vs cool vs archive. Later I have shown Blob Life cycle management policies where you can use wizard to create the Life cycle management policy or even you can use Code View where you can paste your policy using JSON code view.
--------------------------------------------
In the end I have shown a container where the blob life cycle management rule ran automatically. As a few are aware, new developers may think that, Blob Life Cycle Management is not working, but actually It will take around 24-48 hours to reflect.
-----------------------------------------------
#AzureStorageAccount#
#BlobHotvsCoolVsArchive#
#BlobLifeCycleManagement#
-----------------------------------------------
00:00 Introduction
01:22 Hot vs Cool At Storage Account Level
02:30 Hot vs Cool vs Archive Access Tiers
05:32 .net core change access tiers of blob
08:35 Azure Blob Life Cycle Management
----------------------------------------
Hot tier - An online tier optimized for storing data that is accessed or modified frequently. The hot tier has the highest storage costs, but the lowest access costs.
Cool tier - An online tier optimized for storing data that is infrequently accessed or modified. Data in the cool tier should be stored for a minimum of 30 days. The cool tier has lower storage costs and higher access costs compared to the hot tier.
Archive tier - An offline tier optimized for storing data that is rarely accessed, and that has flexible latency requirements, on the order of hours. Data in the archive tier should be stored for a minimum of 180 days.
-------------------------------------------
I have also shown managing the tiers using .net core console application where the .net core console application moved the blobs from Hot vs cool vs archive. Later I have shown Blob Life cycle management policies where you can use wizard to create the Life cycle management policy or even you can use Code View where you can paste your policy using JSON code view.
--------------------------------------------
In the end I have shown a container where the blob life cycle management rule ran automatically. As a few are aware, new developers may think that, Blob Life Cycle Management is not working, but actually It will take around 24-48 hours to reflect.
-----------------------------------------------
#AzureStorageAccount#
#BlobHotvsCoolVsArchive#
#BlobLifeCycleManagement#
-----------------------------------------------
00:00 Introduction
01:22 Hot vs Cool At Storage Account Level
02:30 Hot vs Cool vs Archive Access Tiers
05:32 .net core change access tiers of blob
08:35 Azure Blob Life Cycle Management
3 سال پیش
در تاریخ 1400/08/08 منتشر شده
است.
6,149
بـار بازدید شده