Immutability on Azure storage, how to on existing backups

[fbs@jma.dk]

Hi
We have experienced that it is a problem if we want to move to enable immutability on the Capacity tier in Azure.
We have a SOBR consisting of:
Performance tier (0-14 days) on onpremise SAN
Capacity tier (0-90 days) on Azure blob storage.
Archive tier (90- 365+ days) on Azure archive storage.
This has been working fine, but now we want to enable immutability on the Capacity tier.
According to Veeam Support this can only be done by remiving the existing capacity tier and adding a new one with immutability enable.
To get access to backup data on the old capacity tier we should connect this to a new VBR server, but we have got no answers to how retention and feeding to the archive tier will work !

We need some kind of feature that allows us to have two capacity tier (that are not exactly with same settings) where the old one can be sealed, but feed data to the archive tier until the sealed capacity tier is emptied), and where to data are automatically feeded to the new capacity tier (with immutability).
or
A feature that allows immutability on existing Azure blob capacity tier.

In all the marketing talks on using immutability, they fails to mention what is possible and what is not possible.

Best regards
Finn Busk Sørensen
JMA AS

Reference to Case # 07051343

[Mildur]

Hi Finn

Support is correct.
A new capacity tier is required. You can't enable immutability on an existing capacity tier with Data on it.

We need some kind of feature that allows us to have two capacity tier (that are not exactly with same settings) where the old one can be sealed, but feed data to the archive tier until the sealed capacity tier is emptied), and where to data are

What about creating a new SOBR with a new performance tier (same storage, other folder path) and new capacity and archive tier? This will allow the old offload task still to archive your backups. And new backups will be written to the new SOBR/Capacity/archive tier. After 90 days, you can remove your old SOBR and the old capacity tier.

Best,
Fabian

[fbs@jma.dk]

Hi Fabian
My take to your suggestion is that it could be a useable solution, but it would increase our cost to Azure consumption and we would need to keep the old SOBR for up to 5 years,
as we have data backed up that needs to be available for up to 5 years.
It's possible, but...!
Best regards
Finn