Azure Blob Storage Cold Tier now in production

[svhelden]

In addition to "hot", "cool" and "archive", the new "cold" tier in Azure Blob Storage is now in production:

https://azure.microsoft.com/en-us/blog/ ... available/

Does/will Veeam Backup for Microsoft 365 support this as a primary backup target? And if so, would it make sense? Or would the higher read cost nullify the benefit? (Since reads seem required for copying data to archive storage.)

[Mildur]

Hi Stephan

We are aware of the new tier and are looking into it.
Unfortunately there is no information we can share today.

Best,
Fabian

[johan.h]

You'll note that there is a Veeam quote at the bottom of the blog post you referenced . So yes we intend to support this tier going forward. I expect we'll see support in a coming version of VBR and VBAZ. And I imagine in VB365 eventually as well.

I would highly recommend you do the math very carefully. This tier allows instant access and lower prices, with the tradeoff that writes, and especially retrievals have a higher cost. VB365 uses a lot of metadata that is accessed frequently, so I would be careful with using this one. https://azure.microsoft.com/en-us/prici ... age/blobs/

[svhelden]

What about modifying Veeam for M365 so that it writes metadata to cool or even hot tier but actual items to cold tier?

[johan.h]

Using backup copy jobs would make the most sense. But I imagine that once VB365 officially supports this tier there will be more guidance.