The common requirement for offsite backup is that one Veeam transport service runs in the production site (closer to the source datastore), and the other transport service runs in the remote target site (closer to the repository). During backup, the transport services maintain a stable connection, which allows for uninterrupted operation over WAN or slow links.
Backup to Windows or Linux-based Repository
To perform offsite backup to a Windows or Linux-based repository, you need to deploy a backup proxy in the production site, closer to the source datastore. In this scenario, the source-side transport service is started on the proxy server, and the target-side transport service is started on the Windows or Linux repository server. Backup data is sent from the proxy to the repository over WAN:
Backup to SMB Share
To back up VMs to an offsite SMB share, you should deploy a backup proxy in the source site and an additional Windows-based proxying server in the remote site. The SMB repository should be configured to point to the target-side proxying server. During backup the source-side transport service runs on the source proxy in the production site, and the target-side transport service runs on the target proxying server in the remote site. Backup data is transferred between the backup proxy and the proxying server over WAN:
To have your backups stored and maintained in a consistent state in the offsite location with a minimal load on WAN and production resources, Veeam offers Backup Copy Job (with or without WAN accelerators). Your organization may also wish to deploy Veeam Backup & Replication Cloud Edition to use the cloud storage facilities from the popular providers. Please refer to Veeam Backup & Replication documentation for more details.