Backup Copy Jobs with Azure Object Storage + GFS Synthesizing

[hh_trj]

In Veeam 12, if using Backup Copy jobs to copy backups from a local repository to Azure Object Storage, and with GFS enabled, in what cases would you use the GFS option "Read the entire restore point from source backup instead of synthesizing it from increments"?

I assume that when the option refers to "increments", it's referring to the increments on the target repository (Azure). However, the "Considerations and Limitations" documentation for Object Storage Repositories says "Synthetic full backup method is not supported": https://helpcenter.veeam.com/docs/backu ... ml?ver=120

So, should the option always be checked? If not, are given the way Object Storage works, will it be faster to keep this option unchecked when using Backup Copy jobs to copy from a local repository to Azure?

[HannesK]

Hello,
and welcome to the forums.

I see no reason to ever enable "read the entire restore point" with object storage, because it's a waste of disk space (money). But sometimes customers want it for whatever reason

GFS just works on object storage by marking the needed objects as GFS restore point.

Best regards,
Hannes