I've setup a SureBackup job but it is failing to ping the VM(s) it runs and therefore fails. Could someone please see if I've got my understanding right?
I've monitored what is happening and manually created a dummy VM to play with.
The VMware ESX host I'm using has two vSwitches. On the production vSwitch are three VLANs 4, 5 and 9. My dummy VM, when added to those VLANs, behaves correctly and can see the entire production estate as it should. VLAN 9 is the only one with DHCP on it in my production network, and none of the VMs being restore by Veeam are on VLAN9, so you can actually ignore it.
On the VirtualLab vSwitch (created by B&R) are two VLANs 4 and 5. All production VMs being backed up by Veeam are on either 4 or 5. The gateway for each VLAN is 192.168.4.254 or 192.168.5.254 respectively
When SureBackup runs, the VirtualLab proxy VM that it creates has three IP addresses. 192.168.4.121 in the Production network, 192.168.4.254 in the VLAN4 virtual network, and 192.168.5.254 in the VLAN5 virtual network.
Any PC on the production estate can ping .4.121 when the proxy VM is running, so that side is working.
Any VM within the VLAN4 virtual network can ping each other - EXCEPT none of them can ping the proxy vm on .4.254
My dummy VM is 192.168.4.123 and the VM being tested by SureBackup is .4.23 - they can ping each other ok, but neither can ping .4.254 (the production gateway when live, and should be the proxy vm when in the virtual lab?).
Should SureBackup VMs be able to ping the proxy VM on .4.254 ?
I've screenshotted the VMs as they're running: