Please bear with me, I'm a very green Veeam user, sorry in advance!
Anyway, I'm experiencing an issue with my Veeam/Hyper-V setup.
I have two VM's in my production environment. VM1 is set up with a dedicated NIC on the server (through SR-IOV) and VM2 is set up with a normal virtual switch. Both machines are able to be backed up without issue.
I've created an Application Group containing the 2 VM's. Also a Virtual Lab with advanced single-host networking (basic didn't work, so tried this instead).
ProdSwitch <-> Lab Network Switch - VLAN ID 0 (nothing)
vNIC - Lab Network Switch - MasqIP: 192.168.100.x - Appliance IP 192.168.0.1 (same as our gateway, it filled it in automatically) - DHCP: Yes - DNS: 192.168.0.15 (our production DNS server)
When doing the SureBackup, the Proxy Appliance VM starts fine. Both VM1 and VM2 boot up after that, in that order. While VM1 boots, I go into Hyper-V Manager, and under NIC's, the Lab Network Switch isn't attached to VM1. Warnings messages pop up in Veeam statistics for VM1 as well regarding network being unmapped (check below). I leave SureBackup job running and wait for VM2 to start. When it does I check settings for VM2 and there it is, Lab Network Switch is attached and no warnings are received for VM2.
- Code: Select all
14-06-2014 18:50:03 Warning Preparing configuration
14-06-2014 18:50:03 Virtual machine: name 'VM1', type 'application group', 1024 Mb RAM
14-06-2014 18:50:03 Network 1: production 'VM1', isolated 'unknown', unmapped
14-06-2014 18:50:03 Warning One or more networks cannot be mapped, check virtual lab settings
14-06-2014 18:50:03 0/1 network(s) mapped, 1 unmapped
14-06-2014 18:50:03 Warning Script tests will be skipped because VM is not connected to any private network
Could this have anything to do with the fact im using SR-IOV on VM1? Would seem strange for that to be the culprit, since all Veeam seems to do is remove one vSwitch and put it the Lab Switch.
Any hints, MUCH appreciated