We are running v12 and doing direct-to-azure object storage backups. Everything is working well aside from the fact that the blob continues to grow based on the settings that were set on this KB during initial setup: https://www.veeam.com/kb4416
What I'm trying to understand here is what is the difference between the immutability settings on the repository in veeam and the settings in Azure as the Azure default is to keep versions forever and we need to change this to 30 days but unsure if this is the correct way to accomplish this.
Hello,
hmm, how did you get that option for "keep all versions"? I tried it out for West Europe and US East and I never get that option for selection. I have exactly the same options as shown in the KB article.
So that version option appeared only after the fact. After the storage account was created. We created it a few months ago... Also that's not shown in Veeams KB.
Answering the original question, you should let Veeam manage all blobs in the storage account. No external data lifecycle process should be touching it. If they do, results are totally unpredictable (but nothing good for sure). Thanks!
The issue is that veeam is showing our data in object storage as 5.5TB but the actual usage in object storage is 11TB. The retention is set in Veeam to 21 days and the immutability is set to 30 days...
The retention is set in Veeam to 21 days and the immutability is set to 30 days
That sounds like a good explanation. Instead of 21 days, immutability requires at least 30 days storage. Plus 10 days for block generation and we are at "up to 40 days". More or less double the amount of days = double amount of data.
What is the idea of having longer immutability than retention? The software will try to delete the data after 21 days but that fails because of immutability. Then the background process will clean it up after the immutability period is over.
