Immutable Object Storage retention issue.

[Kazz]

Hi,

We are evaluating Veeam backup for O365 and seeing a retention problem with immutable storage.
In our PoC environment we have 2 buckets (1st does not have object locking, 2nd does) Both buckets are set up with Wasabi.

When setting up storage in Veeam we configured a two day retention on the non immutable repo and 2 days on the immutable.
A backup job was created with a check box for a copy job to the immutable pero. The retention on the immutable repo can't be changed and is expected. We ran out first back up over a week ago and were able to restore from both repos right away. 3 days later, we can no longer restore form the non-immutable repo as the retention for the repo has expired and our backups have been removed, however we can still restore from the immutable repo even after a week which is not expected.

Looking at files placed by veeam in immutable repo on Wasabi we are seeing a lock of 30 days. Does anyone have an explanation why immutable retention of 2 days isn't being enforced ?

Thanks

[Mike Resseler]

What type of backup are you using? Snapshot-based or item-level based? And if I am not mistaken 30 days is a minimum but I would need to verify with our team and with Wasabi to be honest

[Kazz]

Hi Mike,

We are using Snapshot based. No Wasabi does not have a minimum retention setting. It's set by Veeam and it looks like Veeam is not setting the retention correctly

[Polina]

Hi Kazz,

With any retention period, VB365 periodically extends the immutability period to maintain the required duration for all (old and new) sets of backup data. And to save on cost for extending, it by default sets +30 days on immutable repositories. Therefore, with 2 days retention, in fact, the data is immediately blocked for 2+30 days.

[ijross]

Very interesting, are we likely to see similar behaviour for backup chains and immutability for VBR?

[Polina]

It already has a similar mechanism: https://helpcenter.veeam.com/docs/backu ... ml?ver=120