Skip to main content

Hi,
I am running some tests on a demo installation of Veeam. I have set up a job with retention and immutability of 5 days. The full backup is done on Sunday and the incremental on Monday. on 3 August the chain immutability expired but on Sunday 4 August veeam did not remove the old chain (with expired retention and immutability verified by s3 browser) how come?

 

Hi @apaladino -

Welcome to the Community. So, you’re sure the Job’s retention and immutability is indeed met? The only other reason I can think of your restore points are still being retained is due to the Block Generation feature. You can read more about that below:

https://helpcenter.veeam.com/docs/backup/vsphere/hiw_immutability_os.html?ver=120#object-storage-actual-retention

and..

https://helpcenter.veeam.com/docs/backup/vsphere/object_storage_block_generation.html?ver=120


Have you checked how the block generation works?
Usually, we add +30 or +10 days to the retention depending on what you are using as object repository.
We explain better here: https://helpcenter.veeam.com/docs/backup/vsphere/object_storage_block_generation.html?ver=120


Agree with the guys above.  It sounds like you’ve reached your defined immutability, but aren’t accounting for the block generation.


Likely on the 16th day you can purge.  Block generation helps keep your garbage collection and purges manageable in S3. This starts to sound better when you’ve had a garbage collection/purge run for weeks on end..


Comment