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=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyODExIiwiaGFzaCI6ImRjOThhZTUxLWM2MDItNGI0OS04YjI3LWY5Mjc1ODc5MTdiMSJ9
P2V of server targeting original server now re-imaged as a Hyper V host causing network disconnects due to MAC conflict
| KB ID: | 2811 |
| Product: | Veeam Backup & Replication |
| Published: | 2018-12-05 |
| Last Modified: | 2020-08-13 |
Challenge
Instant Recovery of a Veeam Agent for Windows Backup to Hyper V causes network disconnection on Hyper V host when the VM powers on.
Cause
The Instant Recovery VM will be assigned the original server’s MAC address and the NIC will be set to static. If the original server is now the target Hyper V host for the restore, there will be a MAC address conflict causing network disruptions.
Solution
- Restore to a different Hyper V host.
- Do not select power on when restoring and manually set the NIC to dynamic in virtual machine settings in Hyper V manager.
- Do not map the Instant Recovery to a Network and add a NIC manually afterward.
More information
If you have any questions, contact Veeam Support.
| KB ID: | 2811 |
| Product: | Veeam Backup & Replication |
| Published: | 2018-12-05 |
| Last Modified: | 2020-08-13 |
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!
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
