Azure Blob Versioning or not

[dtwiley]

I'm hoping i've missed something but there seems to be conflicting information about this in the documentation:

https://www.veeam.com/kb4416
Under "Storage Account Required Settings"
"Enable 'Versioning for blobs' - Select 'Keep all Versions'"

In the v11 guide: https://www.veeam.com/veeam_backup_11_0 ... erv_pg.pdf
Under "Limitations for Microsoft Azure Object Storage"
"Currently, Veeam Backup & Replication does not support the Versioning feature for Microsoft Azure object
storage. If you plan to use an account with blob versioning enabled, keep in mind this may result in extra
costs for storing objects that have been removed by the retention policy. "

In the v12 guide i cannot find any reference to versioning at all

I ask as we have a client with a 30TB Azure repo which has 18TB in use but Microsoft are charging us for 126TB!!!
Blob versioning is on, should we disable it?

Also, someone had a similar issue and was told to disable versioning:
object-storage-as-a-backup-target-f52/a ... 83511.html

Granted, the first article is regarding immutability, I'm assuming I don't need it if I don't want immutability?

[Mildur]

Hello Dave

Having versioning enabled without immutability is not supported: https://helpcenter.veeam.com/docs/backu ... ml?ver=120

Veeam Backup & Replication supports the Versioning feature for Microsoft Azure object storage repositories for which immutability is enabled.

Enabling versioning without immutability and can lead to the situation you are facing now.
When only versioning is enabled, each deleted BLOB or object is marked as deleted but not removed by Microsoft from the storage container. And because you don't use immutability, our product is not aware anymore of those "deleted" objects. The backup server won't clean them up.

Please disable versioning on your storage container and check with support if deleting the marked as "deleted blobs" is safe.
If you decide in the future to use immutable Azure Blob repositories, then you have to create a new storage account/container and migrate your data to it. Because you cannot enable immutability support for existing storage accounts.

Best,
Fabian

[dtwiley]

thanks, are marked as "delete blobs" the same as previous versions of blobs? I've already kicked off a task to delete all previous versions.

[Mildur]

Yes, "previous versions". I checked in my tenant and deleted blobs are listed as "previous versions".
But I cannot make an official statement or guidance without having access to your environment. That's why I have suggested to check with our customer support team first.

Best,
Fabian

[AlexandreD]

Hello

I'm facing the same issue, versionning had be enable on the storage account in prevision of using immutability, but the customer didn't and we have 60TB of used capacity, and only 15TB used officially by veeam.
There is a way for deleting properly old blobs ?

thank you
Alexandre

[veremin]

It would be best to contact technical support to clarify this issue. We cannot advise you through forum correspondence on which data you can delete and which you cannot. Thank you for your understanding.