Skip to main content

Azure storage account new access tier - Glimpse

Azure has introduced a new access tier for storage account called 𝐂𝐨𝐥𝐝. What is the use of it where we already have 3 access tiers as 𝐇𝐨𝐭, 𝐂𝐨𝐨𝐥 𝐚𝐧𝐝 𝐀𝐫𝐜𝐡𝐢𝐯𝐞?

Let us take scenarios as below.

  1. When our document will get frequently accessed - 𝐇𝐨𝐭
  2. When my document will be infrequently accessed (i.e Within 30 days, it can be accessed. - 𝐂𝐨𝐨𝐥
  3. If my document will be accessed after 30 days, 𝐞𝐚𝐫𝐥𝐢𝐞𝐫 𝐰𝐞 𝐠𝐨 𝐟𝐨𝐫 𝐀𝐫𝐜𝐡𝐢𝐯𝐞 access tier but now
  4. When my document needs to be accessed within 90 days at any time - 𝐂𝐨𝐥𝐝

Data retrieval from Archive needs some process like rehydrating (i.e converting from Archive tier to (Hot or Cool) aka offline tier to online tier).

To save some cost, we can go for cold tier which allows us to keep our data for 90 days instead of archive tier.

Limitations and known issues.

  • The change feed is not yet compatible with the cold tier.
  • Object replication is not yet compatible with the cold tier.
  • The default access tier setting of the account can't be set to cold tier.
  • Setting the cold tier in a batch call is not yet supported (For example: using the Blob Batch REST operation along with the Set Blob Tier subrequest).
  • Hope this tip will be useful.

    Comments

    Popular posts from this blog

    Azure Static Web Apps - Plan Comparison #cloud #azure Hi All! Azure Static web app is a good service when we have static web apps like javacript frameworks and libraries applictions (Ex: Angular, React, Svelte, Vue, Blazor). It also supports Python 3.10 based static web app as well as per the latest azure news. Other advantage of it is coupled with your Azure AD. so that your code can be directly pushed to azure static web app via either Azure DevOps or Github whenever code push occurs. At the time of azure static web app creation, it asks for deployment source as any one of the below. Based on the selection, it allows you to select the organization, project and repositories from the source. Azure DevOps - Azure AD connected Devops organizations will be listed out Github Other - For ex: If you want to deploy code from other organization. Below table will be helpful to choose the best pricing plan for your workload. Plan/Feature Free Standard ...
    Azure Blob - Convert blob access tier on Page and append blobs Hi All Azure storage account is one of the mostly used service by many people and it has page, append and block blob types on storage blob. To have blobs in "Hot" tier incur some more cost but it is prffered for frequently accessed. so if our blob is required but less access then we can change its access tier to keep it with low cost then at the time of need we can change it back to original type. we can set access tier only for block blobs. For remaining blob types, there is no direct way to set access tiers. so how can we achieve it? we need to change blob type to block blob and apply access tier for it then when we need original blob with appropriate, we need to typecast from the recent one we converted. In the below image, Initially I have an append blob called "1.JPG". when you see it, you could not see its access tier whereas bloc blob shows as "Hot" Now, Let's...
    What IP address I can not get it from Azure subnet CIDR to azure resource(s)? What? Will I not be able to get some IP(s) from subnet? How many IP(s) I am not able to get and what are they and why? Azure Virtual Network is one of the main service from azure to create private network in cloud. subnet is the main part of Vnet for segregation. while creating a subnet we have to define CIDR. If I create /24 mask subnet, I should get 256 IP(s) but why am I not getting 256 fully for my resources. I can get only 251 IP(s) because azure reserves 5 IPs from every subnet. consider I'm creating a subnet called DMZ with subnet/cidr range as 10.1.2.0/24 and I'm going to get IP(s) from 10.1.2.4, 10.1.2.5, 10.1.2.6.......10.1.2.254 and please look into the below table for the reason and IP why they are not able to assign to user created azure resources. IP Purpose 10.1.2.0 Network address 10.1.2.1 Reserved by Azure for the defau...