Virtual Lab failing ping, appliance/guest can ping eachother

[nullifi]

I am finally getting around to setting up the virtual lab, and my jobs are failing at the first application group to get the DC up.

It says it is failing the ping test, yet I can go into the console view of both the DC and the virtual lab appliance and I can ping each other. When the job is trying a ping test, who is pinging who? I thought it would be the virtual lab appliance pinging the VM.

[widmerkarl]

Hi Jason,

I had the same problem when i did my first steps with SureBackup and Veeam virtual labs.

In my case the problem was the virtual appliance which had a wrong IP address. I recently wrote a blog post about it (german language):
https://www.driftar.ch/2016/06/06/veeam ... eshooting/

But you can find the hints also in the Veeam helpcenter:
https://www.veeam.com/kb1067

The isolated NIC within the Virtual Lab configuration has to have the gateway address (router / firewall whatever in your network).

[foggy]

Ping requests are sent from the Veeam B&R backup server. Are you able to ping VMs from it?

[nullifi]

Ah, that's probably it, I cannot.

[foggy]

Then please check the KB mentioned by Karl above for possible reasons.

[Zew]

I hope you don't plan on having too many VM's in this test enviro... I've tested it with not so great results. I found after around 3 VM's the timeouts needed to be adjusted as the time it took for these VM's to boot increases as:

1) Each VM has to be "re-hydrated" from their backup files, the more incremental it has to dig through the longer it can take.

2) I/O gets tight the more VM's spin up (I'm not 100% sure how I/O is exactly distributed as Reads are done R/O mode, and Write occur at the PowerNFS mount point, so this really plays a key part).

[lukejf]

Hey Guys, are others having issues with the firewall on domain controllers being set to a public profile? I have checked and not running the vmware adapter mentioned above. I believe this may have something to do with not using the internet gateway proxy option.( read it somewhere on here) The issue is I can't use this as we have services on this server that cannot be connect to the internet as it will cause issues with AV and motoring software. Any ideas

[foggy]

2) I/O gets tight the more VM's spin up (I'm not 100% sure how I/O is exactly distributed as Reads are done R/O mode, and Write occur at the PowerNFS mount point, so this really plays a key part).

The more important fact is that reads are random, so the backup storage random read performance matters here.