Orphaned GFSs from a legacy BCJ not expiring

[GenDev]

A while back I did the BCJ from the legacy jobs to the new style. After the update, I ended up with a bunch of "Disk (Orphaned)" items but then the upgraded jobs continued in "Disk (Copy)". I contacted support a long while ago and they said the orphaned backups will still expire according to retention policies, so I didn't think anything of it. The GFS is setup as 5 weekly, 6 monthly, and 1 yearly.

The problem is, the age of the orphaned restore points are now 450+ days old. Unless I'm misunderstanding, I thought they would've expired out by now.

The oldest restore point on the new "Disk (Copy)" backups is 177 days. Theoretically, I can remove the orphaned jobs but then I'd be missing the "yearly" backups until they come back around again in about half a year.

Am I misunderstanding something? Is the intent that those 450+ day old backups will stick around until the new BCJ's create their yearlies?

EDIT: Just to add, I checked the "GFS Backup Files" report in VeeamOne, and the orphaned backups don't show up in there.

[david.domask]

Hi GenDev,

Thank you for the detailed post -- I'm not aware that background retention would have such a limitation, but it should be visible in the logs as to why it didn't consider these points; can you check the limitations for background retention and confirm if any apply to your situation?

If it doesn't seem to apply, I advise let's have you open a Support Case and please include logs from the Veeam Server itself (select the 3rd radio option "Export all logs for selected components" and select the Veeam server itself)

Please share the case number here once you have created it.

[GenDev]

David,

As far as I know, none of those limitation apply to these jobs.

Case opened: #07315878

Thanks!