- Posts: 1
- Liked: never
- Joined: Apr 01, 2013 3:04 pm
- Full Name: Manuel Zarate
So to illustrate this a little bit we have it setup like this.
VMware Site A ---> VEEAM Remote Proxy A ---> Firewall A <---------------------------> Firewall B <--- VEEAM Backup Server/ Local Proxy B <--- VMware Site B
- VEEAM BAckup Server / Local Proxy B has 2 nics installed: one NIC can reach VEEAM Remote Proxy A, VMware Site A and the second NIC can reach VMware Site B. So in other words this server can see both sites and both environments without problems.
- VMware Site A and VEEAM Remote Proxy A cannot reach directly VMware Site B and viceversa, the only common ground they have is VEEAM BAckup Server/Local Proxy B.
Is the above configuration theoretically right or wrong?
Is it necessary for VMware Site A to be able to communicate directly with VMware Site B or is it enough that the VEEAM Proxies can communicate with their respective VMware environment? Remember in our current setup ESX Hosts in Site A cannot ping ESX Hosts on Site B, however Proxy A can ping Proxy B.
Can the VEEAM BAckup server have 2 NICs configured or can this be part of the problem?
I'm open to any suggestions you may have, im aware that this may not be the recommended configuration so appreciate your inputs. The only thing that cannot change is having VMware Site B on an isolated network.
- Product Manager
- Posts: 22771
- Liked: 1520 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
Users browsing this forum: Google [Bot] and 51 guests