Replication fails to a remote proxy ?.

[iosman987]

Hello,

I have a VBR6 server that needs to replicate to a remote site over a VPN that uses NAT because of duplicate IP addresses at each site.I can reach the vCenter server at the site and replication works if I use defaults for the data transfer settings the replication will be successful. The transfer runs at 4MB/s max and the bottleneck shows up as the target. If I select a VM for the proxy at the remote site to use hot add to write to the SAN, the job fails. I have a support ticket open 5162972. The job log looks like the proxy is trying to connect to the local IP address of the VBR server instead of through NAT. I get the same errors when I try to configure a repository at the remote site. Any suggestions?


thanks
alexsunny

[Mildur]

I‘m pretty sure, that with Veeam, NAT is not supported. Veeam components will always have to connect to the local ip Adress of your servers.

You have to install a vpn connection between the two sites, if you want to use replication.

Another supported configuration is Veeam Cloud Connect Replication. For that, you have to be a service provider or get in contact with your veeam sales contacs to apply for Veeam Cloud Connect Enterprise licenses. Replication is done over Cloud Connect Gateways without the need of a vpn.

https://www.veeam.com/de/cloud-connect- ... ackup.html

I recommend the vpn solution.

[Mildur]

I have done some research and found another possible solution. NAT for veeam components is supported. Only veeam Agent isn‘t possible over NAT
Have you tried this option?

https://helpcenter.veeam.com/docs/backu ... ml?ver=100

If the Microsoft Windows server is deployed outside NAT, in the Preferred TCP connection role section select the Run server on this side check box. In the NAT scenario, the outside client cannot initiate a connection to the server on the NAT network. As a result, services that require initiation of the connection from outside can be disrupted. With this option selected, you will be able to overcome this limitation and initiate a ‘server-client’ connection — that is, a connection in the direction of the Microsoft Windows server.

[foggy]

Right, that option should do the trick.

[iosman987]

thanks my issue has been fixed.