Veeam Immutable with Hardened Linux Setup Help

@SGOMEZ -

Immutability retention is kind of separate from job retention. How immutability with block storage works is the days you configure for immutability (7 days?) doesn't start until after the last restore point in an active chain is created. An active chain is defined as a Full and its subsequent Increments. So when you do another Fill (Friday), that's the beginning of an active chain...which doesn't necessarily coincide with your Job retention.

So, after your Thurs restore point increment is created, the 7 days starts then & all your active chain files are Immutable 7 days from that restore point date. Make sense? 

See here:

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

im not sure i get it that way….lol sorry just new to this type of environment… so my active chain starts fridays because thats the day i do the synthetic full? so everything backed up every day before Thursday its not immutable until that last backup on Thursday? so is it better to say keep 1 restore points instead of 7 days retention policy ?

Restore Points aren't deleted until after 7days from your Thurs increment. 

got it, i have some that immutable period expires on 10/10 and others on 10/14 so when 10/10 hits this points will be deleted, correct?

That should be correct. All files in a given chain...yes. I have some Jobs that have deletes weekly as I have immutability for 7 days. 

i think i understand it now and i guess my setup its somehow correct.

Yeah...you should be all good. Let me know if you have further questions. If any comments provided answered your question, go ahead and mark one as ‘Best Answer’ so others with a similar question who come across your post her will benefit. Thanks.

BTW..the link above has a couple examples in it to help better understand; although..I wish it discussed how immutability interacts with Job retention a bit more. A lot of folks who even read the info in the link I provided, seem to overlook something they should really think about moreso 👇🏻
 

“Immutability retention overrides a Job retention.”

Best.

Shane is right on….so to clarify a bit more, because the oldest restore point is your fill backup, and each day after is incremental, it can’t delete the full restore point after 7 days, 8 days, etc because by deleting that full point, it would render the entire chain invalid because those incrementals all depend on that full.  So after the entire chain has reached your retention policy of 7 days, it can then delete that chain.  This is all entirely outside of immutability.

Also, I don’t want to throw another wrench into things here, but with immutability, there is also a function called block generation which I’m still trying to wrap my head around.

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

So testing myself here, assuming that you have 7 days of retention, and 7 days of immutability set, Veeam will add 10 days of immutability for block gen, so data will actually be immutable for 17 days, 10 days from block gen + 7 days from the oldest restore point in the chain.  After that 17 days has passed, THEN the chain should be deleted.  By my calculation, that means you could have 17 restore points including 3 weekly Full’s in your repository.  Feel free to correct me if I’m wrong.

Block Generation doesn’t apply here because that is only with Object Storage immutability..not Block-based, as is the case with a Hardened Repo. 

so on my case the highlighted ones are my 2 fills and since it expires this Friday  that set from the week  27th to 3rd should be removed  

Ah crap...I missed that it was a hardened repo and not object.  Thanks for pointing that out.  I hope everything else with block generation was correct though if it had been object storage.

so on my case the highlighted ones are my 2 fills and since it expires this Friday  that set from the week  27th to 3rd should be removed  

 

 

Yes, after the backup completes on Friday (11th), the restore points from the 4th on back should be removed per your retention policy.