#1 Global Leader in Data Protection & Ransomware Recovery

Failover or Surebackup Starts a Virtual Machine With an Incorrect Ethernet Interface

KB ID: 1570
Product: Veeam Backup & Replication | 5.0 | 6.1 | 6.5 | 7.0 | 8.0 | 9.0 | 9.5 | 10 | 11 | 12 | 12.1
Published: 2012-04-28
Last Modified: 2023-10-24
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Challenge

When you back up/replicate/copy/clone a vSphere VM running Windows 2008 R2, Windows 2012, or Windows 7 with the VMXNET3 network adapter, the resulting virtual machine obtains a new NIC, and all network settings must be manually adjusted.
Production Machine
Original VM's NIC
RestoredMachine
Resulting VM's NIC

When pinging the VM, a SureBackup job fails with the "Destination host unreachable" error, which can be seen in the SureBackup job log:

Error    [SureBackup] [Name] [PingTest] End 'Network adapter 1: IP address 'xxx.xx.xx.xxx', failed - destination host unreachable'

Cause

This is a known issue with VMXNET3 adapters when used with Windows 2008 R2, Windows 2012, and Windows 7.

For more information, review the following VMware KB Article:
KB1020078: Deploying Windows 2008 R2, Windows 2012, and Windows 7 templates with vmxnet3 renames the NIC as #2 (1020078)

Excerpt from that article:

During template deployment or cloning, new virtual hardware is created for the destination virtual machine. Network interfaces are assigned new MAC addresses. PCI Express devices, including the VMXNET3 virtual ethernet adapter, a new serial number is generated as well.
Windows 2008 R2, Windows 2012, and Windows 7 track PCI devices by which slot the device is connected to. Moving a PCI network interface between slots will allocate a new set of settings for the NIC as it is considered a new device. Replacing a PCI network interface with the same make and model will retain use of the previous settings. However, PCI Express devices are tracked by their serial number, which is derived from the MAC address.
When a virtual machine is created by cloning or template deployment, the new virtual machine's PCI Express virtual network interfaces have different MAC addresses and serial numbers, and are detected as new devices.
The same behavior can be observed by deploying clones of Windows 2008 R2, Windows 2012, or Windows 7 on new physical hardware with PCI Express network interfaces in the same slots.

Solution

More Information

As a workaround, the original machine can be reconfigured to use the E1000 or other PCI network interface.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.