Background:
Been tasked with migrating some Hyper-V machines to VMWARE.
VMWARE converter dosn't support 2008 R2, however there is a nice guild http://sanbarrow.com/p2v2008r2.html#i2which explains one way to do it.
That guild didn't work for me as I as trying to restore Hyper-V IDE disks to VMWARE SCSI disks but was getting the same Bluescreen 7B issue.
Before relasing this, I tried Server 2008 R2's Windows Server Backup, got the same errros, but once I worked out the drive discrepancy issues, I could do a backup to a network location, and then using a windows 7 x64 recovery disk I made do a bare metal restore to VMWARE by using System Image Recovery on a network drive. Was very happy with this :)
So far I've done this to two servers sucessfully.
Issue:
the method mentioned above is failing on one server, first I get the error:
"The system image restore failed.
Error details: The computer needs to be restarted to finish preparing a hard disk for restore. To continue, restart your computer and run the restore again. (0x80042403)"
Now If I try one of the other backups, it just starts restoring. If I restart as recommended I get the error:
"The System image restore failed.
No disk that can be used for recovering the system disk can be found."
it has a details option, that mentions USB drivers, DISKPART, etc, but none appear to be releviant.
Now I've tried backing up to different network locations, ensured that backups are sucessful on the server, trying larger virtual disks but same errors every time.
The server that is failing is Server 2008 R2, with SQL 2008, on a single disk (not best pratice, but this is just a POC box to run a small DB).
All 3 servers have been given identical configurations under Hyper-V and VMWARE.
Question:
So if it works for my other servers why won't it work for this one?
Is is something to do with SQL that's causing it to happen? (wouldn't think so).
Any suggestions on what else I could try?
I know I could just backup the databases and build a new one, but I'm liking this backup method, and if I wanted to use it under a full production senerio I'd like to know how to resolve the error should it arrise.