our Veeam infrastructure consist of VBR/VBEM servers in a remote datacentre and a lot of production sites spread over Europe, on each site we have a Veeam proxy + local repository. Each site has its own lan ip range.
I'm configuring some SureBackup jobs to test backup on sites, at the moment what I need is to pass heartbeat test due it's not possible to pass ping test due to routing issues.
90% of our tests have no issues but some tested VM's, with two vNIC configured, are failing with the error described here : https://www.veeam.com/kb4070
I read the solution suggested but to be honest, I'm unable to replicate it.
Let me show an example (all ip addresses are not real):
Virtual machine with two vNIC.
LAN on vNIC 1:
IP: 10.90.34.56
NetMask: 255.255.248.0
Gateway: 10.90.34.1
DNS: 10.90.34.200
LAN on vNIC 2
IP: 192.168.2.199
NetMask: 255.255.255.0
Gateway : not set
DNS : not set
During the creation of the Virtual Lab I select "Basic single host (automatic configuration)" and this is the result:
Code: Select all
Lab name: Test Virtual Lab
ESX name: xxxxxxxxxxx
Datastore: yyyyyyyyyyyy
Appliance:
Name: Test VLAB VM
Pool name: xxxxxxxxxxx
Folder name: xxxxxxxxxxx
Production network name: Production
IP: 10.90.34.129
Subnet mask: 255.255.248.0
Default gateway: 10.90.34.1
DNS:
Preferred: 10.90.34.200
Alternate: xxxxxxxxxxxxxx
Network configuration type: basic single-host
Network options:
Isolated network: Test VLAB VM Lab Production
Masquerade IP: 11.0.0.0
Appliance IP: 10.0.0.1
DHCP: enabled
Network mapping:
Production --> Test VLAB VM Lab Production
As I said I dont' need the ping test passed, at the moment I need only the heartbeat test and that the whole SureBakup job will not fail.
Thank you for any suggestion.