Veeam: Best practices for Veeam Gateway Server and how to configure it correctly in multi-datacenter environments

Greetings friends, I found myself the other day with an issue I had not seen before, I will explain below the symptoms of the issue, but first let's remember what the Veeam Gateway Server is and what it does in a simple Veeam topology.

Veeam Gateway Server

When configuring an SMB type repository in Veeam, the following options are available:
  • Automatic selection of the server as the SMB gateway proxy (i.e. the server that will host the transport component on the destination side and thus play the role of a data writer to the SMB shared resource itself).
  • Select an specific server (among the managed Windows servers available in Veeam Backup & Replication) as an SMB gateway proxy.
The second option is very useful in situations where the SMB share is in a remote location, as it prevents auto-selection from using a non-local server for the SMB share, so all synthetic operations or backup jobs are performed over the WAN link (which is usually slower than the local link). It is always recommended to use an SMB gateway server as close as possible to the SMB storage. By specifying the SMB gateway we are more likely to keep data flow under control and prevent data from unnecessarily crossing WAN links.