VM not being connected - Virtual Lab

[frankive]

Trying to setup a SureBackup job in our datacenter but no matter what I do I just get "ping test will be skipped. the vm is not connected to any private network". If I go to the hyper-v manager I see that it has the right settings for the vlan and virtual switch, but it will not connect.
If I can connect it manually it all works, but I want to automate the surebackupjob.

What could cause this?

The veeam server is running 2012 R2 with latest Veeam 8. 24GB Ram. Just trying with 2-3 servers in the application group.

[Shestakov]

Hello Frank,
The possible reason is not ideal environment with more than one domain controller (if starting more than one DC in SureBackup job), as DC preparation procedures will be skipped in this case.
Also have you contacted Veeam technical support team? If yes, please provide support case #.
Thanks.

[frankive]

I am only running 1 domain controller in that job.
support case with logs: 00686984

[Vitaliy S.]

What Hyper-V host do you use for the SureBackup job? Is it the same (production one) or a different host? If it is a different one, does it have the same network names as a source host for the backed up VMs?

[frankive]

I am running the SureBackup on the Veeamserver itself which has hyper-v enabled and pretty good with RAM.
So the hyper-v host is the Veeam Server in other words.

No, the name of the virtual swich in the datecenter and on my network card on the veeam server is not the same. Is this an issue which could cause this?
I will try to rename the virtual swich name on my veeam server to the same as my production environment and post the results.

[Vitaliy S.]

Yes, this could be one of the reasons for the message in the SB job log.

[frankive]

And you were right. That solved everything

Case closed!

[nefes]

In future you could add another network mapping rule to your virtual lab instead of renaming virtual switch in infrastructure.