Gateway Server architecture questions

[mikeely]

Looking at the possibility of moving from Veeam Server -> vbr server -> NFS array to Veeam Server -> NFS array and I see that a gateway server is needed. My question is during regular backup operations do the bits need to traverse the gateway server or is it just there to keep accounting data of what's in the NFS share, handle expiry, etc?

[veremin]

They do, as the gateway server will be running target datamover responsible for writing data to target storage. Thanks!

[mikeely]

So the data traverses as follows: Veeam Server -> Gateway Server -> NFS array correct?
Is it recommended to make the Veeam Server (or Veeam Proxy at a remote site) also a gateway server?

[veremin]

Small correction, it goes:

Backup proxy (backup server, if default proxy is chosen) - Gateway server - NFS array

The gateway server should be located close to NFS array (reside in the same site, at least).

Thanks!

[mikeely]

And if the backup proxy/server is on the same network as the NFS server can it serve as both backup proxy and gateway?

[foggy]

Yes, it can fulfill both roles.

[ortoscale]

I'm noticing that linux proxy can't be gateway server? Please correct me if I'm wrong.

[oleg.feoktistov]

It's rather unsupported than can't be. I mean, for instance, I was able to route tcp traffic through linux machine explicitly chosen as a gateway server for S3 storage. So, you can test it for other scenarios, but even if it works, I wouldn't use it in production environments.
Thanks!

[ortoscale]

i can't test it because it's not available to select? any hack?

[oleg.feoktistov]

No hack. My bad, I have failed to mention I didn't try to test it with shares. It's not available for selection there indeed, so there is no way to test it in this scenario. It's still available for object storage though. Thanks!

[ortoscale]

ok, i hope you will solve that in future releases, one can't really say that's linux limitation.