This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 6%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESB%3C/text%3E%3C/svg%3E)
While going through document - https://learn.microsoft.com/en-us/azure/storage/blobs/access-tiers-overview#archive-access-tier, I found that zone redundancy is not supported for archive.
Its bit strange that Local and Geo redundant storage are supported but not the zone one. There exists storage accounts which needs hot (80%), cool (15%), archive (5%) times, but since archive is not supported in zone redundant storage, customer needs to chose higher redundancy resulting in higher cost.
Any plan to support Zone redundancy for archive tier?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(297.6, 81%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAS%3C/text%3E%3C/svg%3E)
Hi Sanjay Bhosale - Thanks for reaching out.
As checked sometime back, there aren't any plans of supporting ZR for archive tier yet. I'll re-check on this again and update the thread.
Hi @Sanjay Bhosale ,
As checked internally, the product group is exploring options but nothing concrete as of now.
Please let us know if you have any further queries. I’m happy to assist you further.
Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
Hi @Amrinder Singh ,
Thanks for the answer.
I have concern where we have to use multiple tiers of blob - hot, cool, and archive. And also we have restriction that data could not be stored in other region due to compliance. So We need to use LRS only in that case, which reduces durability of data. This is concerning us. Any help around it will be appreciated
Thanks
Hi Sanjay Bhosale - Yes, I completely understand your concern however based on the current configurations available, unfortunately that's a limitation although the product group exploring options further.
One option is to explore Cold Tier wherein you land between Cool and Archive tier. The initial write operations will be slightly expensive comparatively but will help on data storage costs.
https://azure.microsoft.com/en-us/pricing/details/storage/blobs/
Anothe option is to move that 5% of data to another account that supports Archive tier but that will be some overhead in terms of moving the data (operation cost).
Hope that helps!
Understood, Thanks @Amrinder Singh