Veeam Backup shows many Orphaned entries all in a sudden?

[Backup.Operator]

I've so many Orphaned backup entries in the list under the Disk (Orphaned):

Just some example.

What makes the backup job to be orphaned ?
How to fix the issue where possible.

Would it be possible to show who made what changes in the Veeam Backup logs?

[Gostev]

It's not a backup job that gets orphaned but rather backup files. Orphaned means that there is no job backup linked to them. This usually happens when you delete the original job, when this happens the backup files are automatically placed in the Orphaned node so that they are not "lost" from the UI perspective and are still available for restores.

There's nothing to fix as this should never happen in normal circumstances but only you perform activities that makes backups lose their connection to a backup job that created them.

As for reviewing who did what changes, you can refer to the Audit log.

[veremin]

More information regarding orphaned backups and background retention (that is supposed to remove them) can be found here and here. Thanks!

[Backup.Operator]

Thank you @Gostev & @veremin

[Matt.Sharpe]

Is there going to be a plan to recover orphaned jobs easier? We have a customer who has accidentally deleted a job. Shows under orphaned, would it make sense to have a 'Recover' or 'recreate' option to add that back to the live job list?

[Gostev]

Something is off in your description, Matt. We don't actually have a place that shows deleted jobs and preserves their settings. If the job is deleted, it's deleted for real. Only backups can optionally remain when you delete a job. But no such option for the job itself, to preserve its "stub" somewhere.