VHR + SOBR + immutability

[Thustra]

Hey

Consider the following setup.

A Veeam hardened repository, on-prem, deployed with the ISO, which in the setup mandates immutability. Unless I am mistaken the 7 days is the minimum you can set it to.
Wasabi storage configured without anything special.

I then configure a SOBR, use the VHR as performance tier and set a wasabi bucket as the capacity tier. We want to minimize the cost of the local storage so it is sized relatively small. We set a policy of moving everything older than 30 days to Wasabi.

How do I set my retention policies here? If I do what I would normally do, 28 incrementals, keep weekly for 4 weeks, keep monthly for 12 months. ( The idea being that only the monthly backup ever goes on to wasabi). What happens with these monthly backups? I would want them to not sit on the local storage, but I assume that due to immutability being applied to the entire duration of the GFS backups all the monthly backups will in fact sit on the on-prem storage for a year. Correct?

Second question when the SOBR policy tries to move the stuff older than 30 days to wasabi, I assume it will "copy" the monthly to wasabi, try to delete it on the VHR, fail because of immutability and .. then what? Will it eventually delete it after a year or just forget about it?

Is using a VHR as the performance tier even viable at all?

[Gostev]

I believe that with the Move policy, the immutability on Performance Tier is truncated according to the Move policy window (so that moves could actually happen) therefore you should be good.

[Thustra]

So does that mean the immutability gets truncated the moment the object lands there? Like I am trying to understand how it actually works. What happens when you add a capacity tier after the fact?

Lets say, similar situation, performance tier is multiple VHR, but now you add the capacity tier after 6 months of only having a performance tier and you set the same move policy of 30 or 40 days. Will it be able to move the "old" monthly GFS backups ?

[Gostev]

This should be well covered in the User Guide btw, I'm just answering from the memory of when I designed all this 5+ years ago.

If you don't have the Move policy enabled and/or Capacity Tier present, then backups on Performance Tier will be created normally of course, that is they will be made immutable for the entire duration of their retention policy. It's quite logical as in this case there's literally no reason to truncate their immutability when they are to stay on Performance Tier for their entire lifetime. Consequently, you won't be able to delete them until their immutability period expires, no matter what you do with your SOBR design later.