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=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyMTM0IiwiaGFzaCI6IjVhYWE5NjhmLTc5MmItNGRjYi05NmNlLTdmZWJkZGVhYzFjZCJ9
1-800-691-1991 | 9am - 8pm ET
EN

multi-OS restore fails on Hyper-V 2008R2

Challenge


To restore individual files and folders from file systems other than Microsoft Windows, you can use the multi-OS File-Level Restore wizard. To restore files from VM guest OS, Veeam Backup & Replication uses a proxy appliance. The proxy appliance is a helper VM running a stripped down Linux kernel that has a minimal set of components. When the appliance is booting up you may open a console and see the following message:
 

Unable to obtain settings by DHCP for interface eth0: ... No such device

Cause


This is a bug in the Linux kernel of the appliance that occurs only in Hyper-V 2008 R2.
 

Solution

This is known issue which will be fixed in the next version of Veeam Backup & Replication.

There are two possible workarounds currently :

  1. Update your Hyper-V server to Windows 2012 R2

  2. Use Instant Recovery, connect VM to an isolated network and retrieve needed files in any convenient way

KB ID:
2134
Product:
Veeam Backup & Replication
Version:
8u2, 8u3, 9
Published:
2016-06-01
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