Recently I ran into a particular issue. We needed a solution to get an offsite backup Grandfather-Father-Son a.k.a GFS with Veeam of the VMs (in this case with HyperV, but it’s the same for VMware),
so we deployed a Storage Gateway at AWS using S3 as a backup repository and config the Backup Copy of the Backup Jobs.
Something like this:
Everything was fine until the execution of a full monthly backup. At this point, we can see that the process that controlled the health of the backup took a long time.
So the solution was to uncheck this control:
Thanks to this great post https://virtualbonzo.com/2018/06/11/veeam-backup-to-aws-health-check/ of @BONZOVT.
But the thing did not end here, another gotcha as Adam said, was when the process of merging oldest restore point into full backup file run.
This process again took a long time, because read entire restore point from backup on S3 and try to synthesize it. But for us, we only need to get a GFS
so a new full from local source instead of synthesizing it from increment, was the solution.
So I marked this option