Link to home
Start Free TrialLog in
Avatar of west-com
west-comFlag for United Kingdom of Great Britain and Northern Ireland

asked on

Issues Restoring a broken physical Server 2008 R2 machine to a Virtual Machine on Hyper-V

I have a physical hardware failure on an old Server 2008 R2 machine. I have plenty of good Bare Metal backups using DPM 2010 and have selected the latest, restoring it to a network share. I've created a virtual machine (on Server 2012 R2 running Hyper-V) and booted the Server 2008 R2 DVD on it, choosing to restore. I've restored from my backup on the network volume.

All seemed to be going well.

Unfortunately, on starting the VM, I get a blue screen within a few seconds, that vanishes too quickly to read. The VM then goes into a reboot cycle.

What step am I missing to notify the restored VM that it is on different hardware with different drivers?
Avatar of Manjunath Sullad
Manjunath Sullad
Flag of India image

For Bare Metal restore process - All the hardware configurations should be same as earlier configuration.  

In your case, I can suggest - Restore it to same or similar physical server, Then you can migrate physical to Virtual (P2V).

What is the exact BSOD Error ?
Avatar of west-com

ASKER

My challenge is that I cannot replicate the existing hardware.

STOP 0x0000007B is the only useful information on the BSOD screen, now that I've worked out how to disable automatic restart on system failure from the F8 screen on booting
ASKER CERTIFIED SOLUTION
Avatar of noxcho
noxcho
Flag of Germany image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Many thanks for this. At present, I cannot grade more than C, as I need to purchase a copy of Paragon Disk Manager to confirm, but at least it's pointing me in the right direction.
Oh my Lord, so many typos in one answer of mine :) I hate iPad :)

And thank for the points.
Happens you have question on P2P let me know.