Video Screencast Help

Problem with VM-Restore with adapter Typ VMXNET3

Created: 01 Jul 2012 • Updated: 02 Jul 2012 | 2 comments
Tom Egger's picture
This issue has been solved. See solution.

NetBackup master server on (linux) and backup host (Windows)

we have a problem with the restore of a VM VMXNET3 of the adapter type.

Netbackup from view, everything is ok, but I can not ping the VM.

Did you perhaps have an idea?

Comments 2 CommentsJump to latest comment

Stuart Green's picture
If the Guest OS VM is Windows 2008 R2  AND VMXNET3 is the NIC adapter used then yes there is a small known issue.
You need to install a MS hotfix.
This should be well highlighted to folks out there, in this scenario.
Affected Systems: Windows Server 2008 R2 X86 and X64
This fixes the issue when cloning or restoring a VM with the affected OS and a new NIC is created instead of the expected original NIC
Deploying Windows 2008 R2 and Windows 7 templates with vmxnet3 renames the NIC as #2 (general information from VMWare) (Patch from Microsoft for Windows 2008 and Windows 7 without SP1) (Patch from Microsoft for Windows 2008 and Windows 7 with SP1)
The correct OS version hotfix should fix the problem of renaming the NIC.
Get your VMware admins to install this hotfix into any of their templates that use these OS and Virtual NIC.
(Yup we found this out immediately with Veeam SureBackup.)

Tip: Get overview/document your NBU environment. Run 'nbsu' and review the output.

• If this provides help, please vote or mark appropriate solution.