Object Storage as Backup Target • Re: Object Storage and Immutability principles

I spent the whole weekend reading other discussions here on the forum and re-reading the explanations in the documentation. I think I understood Checkpoints. But I still wasn't clear about Actual retention. I guess I misunderstood how Immutability is extended (I thought it was only during merge operation, but sometimes the entire Backup Chain wouldn't be protected).

Finally, I tried to draw it. Are my following assumptions correct? (the description doesn't have the exact terminology)

A new Checkpoint is created for each backup. Restore Points belonging to the Backup Chain from the previous Checkpoint are used in it and a new Restore Point is added. If the objects (Restore Points) from the previous Checkpoint do not have the same Immutability as the new Restore Point, their Immutability is extended.

Another thing is the application of the Retention Policy.

• Restore Point is created, Immutability is set (Immutability Period + Block Generation Period)

• Immutability is extended to previous Restore Points (is it done now or after merging?)

• if retention is exceeded, then the Full Backup is merged with the previous Incremental Backup (within Checkpoint)

For the example I used the values:

• Immutability Period 10 days

• Block Generation 10 days

• Retention Policy 20 days

If it works like this, then a lot of things make sense to me. In Veeam I see (after a certain time) 20 Restore Points. There are 40 on the object storage and I can go back to them (Powershell).

I tried to draw the course of different days schematically. They are individual generations below each other, where the Immutability Date is always the same (even extended).



Thanks for all the advice.

Statistics: Posted by Samuraj — Feb 17, 2025 7:57 am

---