S3 immutable time is more than configured

[MMASLOUH7]

Hi,

I'm testing the immutable option of AWS s3 and Wasabi, I set the backup to be immutable for 3 days and i started the backup job, everything goes well and i made a restore test.

After one week and when I tried today to delete this backup from the both object repositories, it failed with an error meesage told me that I canot delete this backup before March 9, 2023.

is there any explanation for this problem, thanks.

[jorgedlcruz]

Hello,
If I am not mistaken, some Hot Object Storage providers, like Wasabi, have 30 days minimum. That is what you might be experiencing.

[sfirmes]

What you are seeing is block generation. This explains what block generation is https://helpcenter.veeam.com/docs/backu ... ml?ver=120.

Hope this helps.

[chrisWasabi]

Hello,

This is due to the Veeam feature of Block Generation, you can read about it here: https://helpcenter.veeam.com/docs/backu ... ml?ver=120. This means that the number you set in Veeam is the minimum it would ever be, not the maximum. You can look at when your Object Lock will expire in the Wasabi Console, enabling the Show Versions Slider, then clicking on an Object. Relevant KB: https://wasabi-support.zendesk.com/hc/e ... ject-Lock-.

Wasabi does have a Minimum Storage Duration Policy, however this does not prevent you from deleting an object as soon as it is uploaded. https://wasabi-support.zendesk.com/hc/e ... licy-work-

Thanks,
Chris

[MMASLOUH7]

Thank you guys for the info