Merging incrementals backup copy job

[Ben123]

Hi

We have a veeam backup and replication server V10 creating backups to a QNAP SMB fileshare in the LAN. Recently we have added another QNAP with SMB Fileshare in another location so we can make backup copies to it. However the uplink is quite slow and particularly the merges are taking forever to complete.

Would it be possible to add either a Veeam Backup Gateway or Backup Proxy to the remote site to speed up the merges after the copy job completes? Is there any other advice that could possibly speed up our backup copy job to the remote site without needing to speed up our internet?

[Andreas Neufert]

No, this is the way to go as the merge transport data otherwise over the WAN 2 times.

Potentially you can add the QNAP as a Linux Repository (don´t know if you get root for it). This could help to avoid the additional backup server.

Important point as well is to enable write-through support on the SMB share or use it with iSCSI/NFS instead if not available.

[foggy]

Also, consider using WAN acceleration for optimal data transfer over a slow link.

[Ben123]

No, this is the way to go as the merge transport data otherwise over the WAN 2 times.

You mean with a gateway server at the remote site is the way to go?

[Mildur]

Yes, ben
Doing that will reduce needed WAN traffic dramatically. Only changes (vib) will send to the remote site.
Without gateway server on remote site, veeam will transfer the „vbk data blocks“ and „vib data blocks“ back to your primary site, synthesize the full, and transfer the new vbk data blocks back to the remote site.

With gateway server, only changed data will be transferee to remote site, the gateway server on remote site will read the „vbk data blocks“ and „vib data blocks“ and synthesize the new vbk file.
They will no get transferred back to primary site, because you have an veeam gateway server in the remote site which can do all the work.

[Andreas Neufert]

Gateway Server for SMB/NFS or Windows Repository Server for iSCSI.