retention not being honored

[infused]

Hi Guys.

v10, I have two backup jobs that have 50 retention points. Only one full backup. They are set to only have 14 retention points and full synthetic backup on the weekend. This isn't happening. I've just nuked the points as I have to free some disk space, but any idea on why this would happen?

The other 20 odd jobs which have the same settings are not affected.

[HannesK]

Hello,
what is your case number (the topic will be deleted without case number)?

With 14 RPs and weekly synthetic, you should not have more than 20 restore points (assuming that you run only one daily backup).

Best regards,
Hannes

[infused]

case #04192590

[foggy]

Hi Hayden, any chance those two just do not run on the day the synthetic full is scheduled at? This might be the case if jobs chaining is used, for example.

[cwagz78]

I am seeing the same issue with all of my machines. v10 community edition. Case 04194144.

[foggy]

Hi Chad, thanks for providing the case ID. The same question to you - are you chaining jobs, meaning scheduling them to start one after another?

[cwagz78]

I do not believe I am chaining jobs. I just have one schedule that starts at 2AM. It includes 8 targets. They seems to wake up in some order and then get backed up.

[Egor Yakovlev]

Hi Chad and Hayden.
I have checked your cases and encourage you to work patiently with support - both cases seem to have identical problem on first glance, however as per attached logs they are totally different by nature. I will keep an eye on the resolution process.
/Thanks!

[infused]

Missed the replies, but to let you know the full's are being done. I've kicked off fulls manually as well and it's not rolling up. Getting to the point soon where we have to delete the backup data as we are running out of space.

[rhys.hammond]

I saw a similar issue for a customer a few weeks agos. In their case, it turned out they were running low on disk space where the repository was configured so Veeam didn't have enough space to create a new full backup. What is the size of the full backup and how much free space is remaining on the backup repository?

[infused]

Not my issues, 4tb free, synthetic is only 500gb.

Veeam support has just replied saying nuke/move the chain... so this has to be a bug. I suspect it's got something to do with linked jobs.

[Dima P.]

I've kicked off fulls manually as well and it's not rolling up. Getting to the point soon where we have to delete the backup data as we are running out of space.

If you run the job with periodic full backups then olders backup chain is being removed only after latest increment is retied. Here is the link to Help Center. If your repository is running low on space you can switch the job to run without periodic full backups, then merge will be performed as soon as retention is reached. Cheers!

[infused]

Take a look at the ticket - I don't think this is the issue.