Hardened repository on other location - NAT or Site2Site VPN tunnel

[BostjanUNIJA]

Hi.
Current environment:
* Multiple dedicated virtual servers in a custom vendor cloud environment.
* VBR is also in current custom vendors cloud environment.
* The idea is they would like to add offsite hardened repository which is located in xy datacenter.

If we wish to deploy and represent this hardened repository to VBR, is Site-2-Site VPN tunnel between VBR and datacenter 'a must'?
Or VBR will be able to communicate and translate NAT to get to this repository?

[pybfr]

No, you can not use NAT between Veeam components.

[BostjanUNIJA]

Hi.
Thank you for your reply.
I expected that kind of answer, as I had similiar scenario in the past.
Any word on a long run will Veeam ever support NAT environments?

[pybfr]

Probably not since it would introduce a lot of variables in the data flows within the platform with all the consequences in term of reliability and performance (and as such would place the burden to troubleshoot the whole architecture on Veeam support).
Using Cloud Connect is usually the way to go in distributed/segmented setup but it may be overkill for a single repo.