v12 Backup Copy Jobs and Orphaned Backups with GFS

[GenDev]

I recently converted my legacy backup jobs to v12. I followed allow of the proper instructions and mapped the orphaned backups to the new jobs. Right now, the new v12 BCJ is running fine adding new restore points to "Disk (Copy)" instead of "Disk (Orphaned)". My main concern is the GFS retention of the orphaned files.

I spoke with support (Case 05998856) and they mentioned that, even though the backups orphaned, they are still subject to their previous GFS settings and will eventually expire out. I'm not so sure I'm seeing that. The GFS on the orphaned backups had a settings of "5 weekly, 6 monthly, and 1 yearly". If I'm assuming correct, the orphaned backups should delete one "weekly" each week and it'll be replaced by a new "weekly" in the new "Disk (Copy)". This isn't happening. The "Disk (Copy)" continues to add weekly's but nothing is happening to the "Disk (Orphaned)" files as the number of restore points has not changed at all.

I didn't realize until this morning that VeeamOne can show the expiration date of GFS restore points. All of the backups "Disk (Copy)" have an "Expiration Date" listed. All of the backups in "Disk (Orphaned)" are listed under "Restore Points with no Jobs" and do not have an expiration date.

Can someone give me some clarification on this? I don't want the restore points from "Disk (Orphaned)" just sitting there, taking up space, and not expiring.

[Mildur]

Hi GenDev

Support statement is correct. GFS backups will age out accordingly to their retention settings. You may check out the explanation in our user guide for the background retention job:
https://helpcenter.veeam.com/docs/backu ... ml?ver=120

Do you see all gfs restore points of those jobs in Disk (Copy)? Even the old ones created by V11?
I assume, those restore points in Disk (Orphaned) are the leftovers from the migration. If so, they may be deleted. I would check that with the engineer from your support ticket. Without having access to your infrastructure, I cannot confirm if you can delete them safely.

https://helpcenter.veeam.com/docs/backu ... ml?ver=120

[For format upgrade using mapping] During the upgrade, Veeam Backup & Replication synthesizes full backups in the per-machine backup with separate metadata files format using the existing backup (the source for mapping). That is why you need enough space on the repository to store full backups. After the successful change operation, the backup used as the source for mapping is placed to the node with the (Orphaned) postfix. After the successful upgrade, you can delete this orphaned backup.

Best,
Fabian