Feature Request: Keep Synthetic Fulls (GFS) with per-machine backup files even if copy job fails-bac

[Virtuollie]

Hello,

While working on the issue in Case #04982993 (Backup Copy Job fails with message "Transmission pipeline hanged, aborting process. Error: Error in the application"), I noticed that even if synthetic full backup files had been created for a majority of VMs, the failure of the Backup Copy job later on in the process results in deletion of the full backup files, so creation of weekly or monthly full backups starts from scratch the next day.
I would strongly suggest to change that behaviour, so the job can update the metafile to keep the already accomplished tasks and create synth fulls only for the few VMs that were not finished when failing.
In my case the copy job failed at 98% completion after over 20 hours runtime and then started from scratch....

Best regards,
Ollie

[Dima P.]

Hello Oliver,

Will be fixed in the upcoming major version on Veeam B&R. Thanks!