VMXNET3 and SureBackup

[darryl.crossley]

Morning all,
Is anyone successfully using VMXNET3 network adapters and SureBackup?

I've seen and applied all the Veeam Forum threads, the VMware KB articles and Windows hotfixes and still cannot get it to work correctly. The MAC address change is still causing Windows to change the adapter to a new DHCP adapter. I'd be interesting to know if anyone is using this setup in the wild, I've tried to get this working in numerous environments without success.

Darryl

[Gostev]

Yes, the Windows hotfix mentioned worked for everyone who applied it in the wild, if that is what you are looking to hear... first time I hear it is not helping.

Official VMware support KB on this issue (for future readers):
http://kb.vmware.com/selfservice/micros ... Id=1020078

[Cokovic]

I'm using it here successfully in our environment and i can confirm that this Microsoft hotfix is still working and applicable for VMXNET3 and Server 2008 R2.

Did you try to create a new active full backup of your VM after applying the hotfix and use this one in your SureBackup job? An incremental run should be fine too but i would give it a try.

[paps40]

I have just started seeing this issue again in my environment running Veeam 7.0.0.839 and Server 2012 (Veeam Ticket 00572945). All of my sure backup jobs are failing when trying to run the test scripts. They are failing because the SBJ DC has a new nic with a different mac address which is causing other vm's (SQL, Exchange, etc) that are dependent on that dc for communication to not work correctly.

Does anyone know of a fix for this? Alot of the articles I have been reading pertain to win 7 and server 2008 not server 2012. I was under the assumption that veeam 7 and server 2012 don't have this issue anymore. We are running vsphere 5.1.

URL's
http://kb.vmware.com/selfservice/micros ... Id=1020078
http://www.veeam.com/blog/mac-address-c ... apter.html
http://support.microsoft.com/kb/2526142

Thanks.

[foggy]

Peter, we were not able to reproduce this internally so far, using the latest Veeam B&R version and Windows Server 2012. We will continue investigation once/if we get more occurrences of the issue.