https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxNjAxIiwiaGFzaCI6ImY5ZmYzZGI0LTc0MzgtNDM5Ny1iYTNhLTRlODUzMTRiZWU1ZSJ9
1-800-691-1991 | 9am - 8pm ET
EN

Re-IP issues: Win2008R2 with VMXNET 3 Adapter

Challenge

When you perform failover for a Win2008R2 server with a VMXNET 3 Adapter, configured Re-IP settings are not applied to the target replica. Instead, the replica acquires another IP address.

Cause

This is a known issue with the VMXNET 3 Adapter. When Veeam Backup & Replication creates a VM replica, the replica’s PCI Express virtual network acquires a MAC address that differs from the MAC address of the source VM. This MAC address is ultimately added as a new device, so Re-IP does not function properly.

Solution

Information regarding solutions and workarounds are discussed in the following VMware article.

Deploying Windows 2008 R2 and Windows 7 templates with vmxnet3 renames the NIC as #2 (1020078)
 


After following the instructions in the above VMware KB article to either resolve or workaround the issue, the following steps should be performed to update the replica.
  1. Delete the current VM replica.

  2. Verify Re-IP settings in the properties of a replication job.

  3. Re-run the replication job.

  4. When a new replica is created, test failover to make sure that Re-IP settings are applied properly.

KB ID:
1601
Product:
Veeam Backup & Replication, Veeam Cloud Connect
Version:
All
Published:
2012-05-30
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later