we are running several IP networks inside a single production Network on ESX5.5, and our Surebackup Jobs are failing since the upgrade to V9.5.
My production setup is like this (I know this is not best practice, but sometimes things get handed over to you and you have to live with it):
- one production network on three ESX 5.5 hosts, called "VM Production"
- multiple IP networks inside this single LAN
-- 192.168.1.0/24 with default GW 192.168.1.254 - this is where most servers live
-- 192.168.2.0/24 with default GW 192.168.2.254 - a management network
-- 192.168.3.0/24 with default GW 192.168.3.254 - servers for a separate project
- all these Default GWs are virtual IPs on a single Network port on the physical firewall device. No VLAN tagging in place.
All ~50 VMs on this Cluster are backed up using VEEAM 9.5, and replicated to a fourth (legacy) ESX 5.5 host with two datastores.
So i have two replication jobs, one for each datastore on the replication host.
Up until VEEAM 9 we had a weekly Surebackup Job set up that would test all VMs on the replication host. The Virtual Appliance was configured for Advanced Single Host Networking, with one single Isolated Network, and multiple vNICs in Network Settings:
- vNIC1: Masquerade IP 192.168.255.x, Appliance IP 192.168.1.254
- vNIC2: Masquerade IP 192.168.254.x, Appliance IP 192.168.2.254
- vNIC3: Masquerade IP 192.168.253.x, Appliance IP 192.168.3.254
This was working fine until the upgrade to V9.5. The appliance failed to start and I redeployed it, and afterwards servers in the first network could be verified successfully, but servers in 192.168.2 und .3 would still fail. I logged into the appliance and couldn't find any reference to these networks, so i decided to rebuild the appliance.
Unfortunately it would not allow me to create multiple vNICs for the same Isolated Network: "vNIC with such isolated Network connected already exists".
Support told me this setup was not supported and I should file a feature request (Case ID is 02029961). As this was working in the past I'd rather think this is a bug report
Any idea how to set this up in V9.5? Separating the single Network into multiple vLANs is not an option on the physical network, I'm afraid.