- Posts: 2
- Liked: never
- Joined: Dec 08, 2011 7:07 pm
- Full Name: Conrad Schissler
In v5, we used the "initial replica to removable storage" option to seed the replicas so we could physically carry the data to our site, and it worked great.
In v6, as anyone who's taken a look has seen, this now works in a completely different way. I've got my proxies set up at both source and target locations, and I've got my WAN jobs running again, but the IP configuration I've got set up seems...overexposed.
In order to get it working, I've had to give both the target proxy and target ESX host public IP addresses, because without having a public IP on the ESX host, I can't add it as a server on the Veeam source installation.
Given the proxy architecture, it would seem to me that I should be able to add the remote ESX host by a local IP address that is only accessible to the remote proxy server (so I don't have to expose my ESX host publicly), but I don't see any way to do that.
Am I missing something, or is it not currently possible to set it up like that?
- VP, Product Management
- Posts: 5959
- Liked: 2809 times
- Joined: Jun 05, 2009 12:57 pm
- Full Name: Tom Sightler
V6 didn't really change the requirements for IP networking over V5. Just like in V5 the V6 server must be able to talk to the vCenter server (highly recommended) or the ESXi host (if adding directly). The proxies must be able to communicate to each other, and the Veeam server.