Re-IP issues: Win2008R2 with VMXNET 3 Adapter
Challenge
Cause
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.
-
Delete the current VM replica.
-
Verify Re-IP settings in the properties of a replication job.
-
Re-run the replication job.
-
When a new replica is created, test failover to make sure that Re-IP settings are applied properly.
Couldn't find what you were looking for?
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
Do you have an issue or need post-sales technical assistance?
*if you need help choosing the right product, please select "Sales" chat
Do you need guidance on the website, upgrade hints or help with your licenses/accounts?
Questions regarding your Veeam contract renewal? Contact us and learn how you can maximize your savings
Do you need additional license, pricing details, product information or have any other sales-related question?
Would you like to become our partner or do you need assistance as our existing partner?
We apologize, but this chat is not available at the moment
We apologize, but this chat is not available at the moment
We apologize, but this chat is not available at the moment
We apologize, but this chat is not available at the moment
Veeam representative will get back to you shortly.
