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

    Post a Comment

    Popular posts from this blog

    Azure Public IP(s) are zone redundant free of cost natively - Generally Available Availability zone gives high availability to an application as well as information by forestalling the physical datacenter disappointments by involving replication of the asset in extra datacenter. Azure typically has 3 zones per region (and not all regions support zone). Thus, while setting up the environment we really want to pick the right region based on our usecase. Public IP helps to access a resource or an application publicly. Azure offers 2 types of SKU for public IP as below Basic Standard Only Standard SKU gives zone facility. Basic SKU is always non-zonal and this SKU also will be retired 09/2025. Standard public IP can be fell into any of the below category No Zone / Non-Zonal - No availability zone at all Zonal - Our services can be replicated in any one of selected zones from three zones. Zone redundant - Resource will be replicated in all 3 zones. It is opposite of...
    Post a Comment
    Read more
    create and read a file in Linux As a cloud and Devops engineers, we need to know to work with Linux is always helpful to handle some critical situations. There are multiple ways to create and read a file in Linux. In this article we're going to learn about touch command. Let's work with followings in this article pwd - To show present working directory touch - To create an empty file ls - To list the files from the current directory echo - To display message as well as write into a file. '>' - write into a file. '>>' - append it to a file cat - To read content of file we'll see writing and appending into a file in my upcoming post.
    Post a Comment
    Read more
    Avoid YAML Validation error in azure devops pipeline Hi All! Consider a scenario that you committed a YML CI/CD file on the repository with some syntax, indentation and/or other error(s). so that pipeline failed. After you find some errors and rectified in the repository file and committed again but pipeline still gets failed because some errors are still there. Now you afraid that even if you fixed error in all the places, what happens if pipeline failed again because your project lead or manager set up build notification mail trigger for build success and fails. you need to answer them for build fail reason. Azure devops pipelines offers YAML validation feature after altered and before committed and before run pipeline. To utilize this feature, what we do is, Instead of modifying the file from repository, Do as below Go to the specific build click "Edit Pipeline" Modify/fix errors and click "validate" as shown in the picture below ...
    Post a Comment
    Read more