Excessive Restore Points

[Zew]

Quick Q I hope someone can help me with. I was doing an audit of the backsets I have and the first system I checked for the backset of had 2 chains, one with 7 restore points, and the other with 135 restore points... Considering I created the jobs I knew this didn't seem correct. I checked the associated job and sure enough in the jobs state restore point to retain is set to 6.

Now for the older chain which was well past our retention guidelines, I simply right clicked the chain and selected "delete from disk". But the Chain with 135 restore points (that should only have 6) is not exactly something I can simply delete. I COULD just do that and re-run the job and it's create a new active full and future run jobs will be intermediary. For this specific machine it's proably OK to do this.... BUT if I had a system where retaining the existing restore point up to that defined in the job... How the heck do I fix this?

[Zew]

*Update* I read this Veeam thread: vmware-vsphere-f24/more-restore-points- ... 65065.html
Which lead to this Veeam KB: https://helpcenter.veeam.com/archive/ba ... ental.html

Even then it doesn't make sense... The main Full VBK in the chain is from 2017, and every other file in the chain is a VIB (Incremental) and there's a gap between the main full VBK (2017) and the first VIB which is dated (2022)... this chain is entirely messed as far as I can tell and is completely not following the stated process. I'm also worried in these situations deleteing the old chain and starting a new one from scratch is the only real solution here... which is kinda garbage...

[tyler.jurgens]

It is very hard to diagnose this kind of thing over the forums - you will be asked to open a support ticket.

However, what looks like has happened is you may have merge issues with that backup chain, causing more backups to pile up. As for the gap in dates - could be caused by simply having backup failures or some other problem.

I would suggest taking an Active Full backup and monitoring that backup chain to see if it continues to merge appropriately as you get to the retention limit. If it doesn't, that would be another ticket with Veeam and have them help diagnose why the backups aren't merging as they should.

[Zew]

Created a support case is what I did, cause it's clearly broke.
Case #07478172