Prior backup chain not removed after x days

[McKITGuys]

Hi,

I have a backup set where the newest backup chain is encrypted but the older one is not. I tried to get rid of the older chain by changing my retention days to 2. The older chain's last incremental is March 2nd so I thought by now it would have deleted that older chain (the older set goes from Feb 28th for its .vbk to Mar 2 to the last .vib in the chain; the new Active Full .vbk started on March 4th).

The new encrypted .vbk was triggered by doing a manual trigger of "Active Full" as I did not want to wait until the end of the month (when active fulls are normally done via the "Last Friday" setting) to have a new encrypted backup set started.

Why would this not automatically delete the 2nd oldest backup set - it is more than 2 days after the last incremental point? Is there any way to get rid of it manually?

Thanks.

[PetrM]

Hello,

My only guess is that you don't have at least 3 restore points in the recent chain, as stated on this page:

The minimum number of retained restore points is 3. This number does not depend on the number of days set in the retention policy. For example, the retention policy is set to 5 days. You launch the job after it was stopped for 10 days. Normally, Veeam Backup & Replication would delete all previous restore points. However, due to the minimum number of retained restore points, you will still have at least 3 restore points: the newly created restore point and the two previous ones.

If it's not the case, I suggest contacting our support team and asking our engineers to review the job settings and your infrastructure. I'm sure they will come up with an explanation very quickly.

Thanks!

[McKITGuys]

That would be it! The jobs only had the one full .vbk and one incremental .vib each. Thanks.