Replication Error - no data of the requested type was found?

[Virtualizer]

Hi all

just recently upgraded to veeam b&r v7 and i'm happy with it.

we have here one b&r server and two proxies over two sites.
these two proxies we have setup are VMs.
we have VMware vSphere 5.1 implemented.
the replications worked pretty well until i made a change.
i changed the VM's network cards to VMXNET3 instead of E1000 for increased performance. Made sure all ips are set correct with the replaced virtual network card.

After that change, the replication jobs stopped working.
They all output the same error on every processed vm:

9/12/2013 9:56:35 AM :: Job started at 9/12/2013 9:56:34 AM
9/12/2013 9:56:35 AM :: Building VM list
9/12/2013 9:57:16 AM :: VM size: 2.5 TB
9/12/2013 9:57:16 AM :: Changed block tracking is enabled
9/12/2013 9:57:19 AM :: Preparing next VM for processing
9/12/2013 9:57:19 AM :: Processing 'server1' Error: Client error: The requested name is valid, but no data of the requested type was found

9/12/2013 9:57:21 AM :: Preparing next VM for processing
9/12/2013 9:57:21 AM :: Processing 'server2' Error: Client error: The requested name is valid, but no data of the requested type was found

9/12/2013 9:57:23 AM :: Preparing next VM for processing
9/12/2013 9:57:38 AM :: Processing 'server3' Error: Client error: The requested name is valid, but no data of the requested type was found

9/12/2013 9:57:40 AM :: All VMs have been queued for processing
9/12/2013 9:57:54 AM :: Job finished with error at 9/12/2013 9:57:54 AM

i checked the proxies - all seems good, there's ping and jobs are set correctly and nothing has changed.
there's ping from these proxies and i even re-scanned my virtual machines to make sure all is properly discovered.

backup job still work well and (proxy selection in these jobs set to automatic selection)

any idea what went wrong ?

[veremin]

Even though there previously have been issues with replicating VM that has vmxnet3 device, none of them seems to be related to your case. So, it might be worth opening a ticket with our support team and letting them investigate it directly.

I’m also wondering what happens if you create a new replication job and try to process VMs in question there. Will it also fail with the said error or not?

Thanks.

[Virtualizer]

Hi,

I just tried that. Created a single replication job with one of the VMs that wont replicate. Still no good.

Why would VMXNET3 make a problem ?

[veremin]

Corresponding logs should answer this question for sure. So, please, contact our support team and provide them with required log files.

It will be also appreciated if you update the topic with ticket number, so that, we can follow your case and share the resolution once it’s found.

Thanks.

[Virtualizer]

Okay

I somehow solved this. Just to let everyone know.
What i did is added back the E1000 NIC on the source proxy. change it's dhcp settings to auto. making sure it is completely reset.
removed both NICS.
Added again VMXNET3 card and set from scratch dhcp settings.

Now replication on the single job i just made for test, works !

Gary.

[veremin]

And what about previous replication jobs? Did they also get back to normal again or not? Thanks.

[Virtualizer]

Will test it tonight as these jobs might actually work and they are pretty intensive.

Will report back later.

Gary

[veremin]

What i did is added back the E1000 NIC on the source proxy.

Just a follow-up question: Have you originally changed network device type of replicated VMs or of proxy servers, instead? Thanks.

[Virtualizer]

if i got your question right,
I changed the NIC on the Proxy server. not the replicated server.

[veremin]

Hmm, I’m not sure how changing NIC type of source proxy server might have affected VM processing. Though, if the said error persists with night replication jobs, you can try to re-add proxy servers to a backup console and see whether it helps or not. Thanks.