BMR V2P VMware to Physical Server

[Redgate]

Hi

Tried to challenge myself yesterday with a Virtual-2-Physical BMR on Windows 2003.

VMware5, VM with 4 CPU, Windows 2003 backed up with D2D r16 update 7
Created a BMR DVD from D2DBMR.ISO and copied the drivers from physical server in the D2D gui on to the dvd.

Physical server, Dell 2950, 1 CPU
Boot the physical server and restored the D2D backup of the virtual server. The BMR process injected the DELL Raid driver but I did not manage to manually inject more drivers from the DVD. First time it was bluescreen.
After a few tests I did the "old" way, manually copying hal.dll, ntoskrnl.exe and 4 more files to the BMR restored server and now the server boots up with Windows 2003 but soon I get a bluescreen again.

BMR test backing up Windows 2003 on that physical server, erasing the boot-disk, restore the D2D image works just fine, so the server, the backup and restore process is OK when I am using the "original" Windows 2003 server installation.

So, is V2P (Virtual-2-Physical) BMR supported on that different hardware (VM with 4 CPU to physical server with 1 CPU) and using Windows 2003 ?
If that is the case, what went wrong ?
I used the D2DBMR.ISO that is included in the D2D r16 download, or should I use a Windows 2003 Server install CD instead ?

Regards
Mats

[Pratap Karonde]

Did you use the D2DBMR.ISO that came with update 7?

Did you have to use any Dell RAID drivers for the disks to be visible in the BMR UI? Or were the disks accessible without using any drivers?

Can you elaborate on what you mean by “but I did not manage to manually inject more drivers from the DVD”?

[Mats Brodin]

Hi
it is the iso that come with update 7
the BMR found the disks without any extra driver, but when the BMR process was finished it automatically injected the Dell raiddriver. (I tried without the driver as well)

what I mean is that in the driver utility window that shows the server I could not find any suitable driver though I collected them earlier from the Dell server.

hope that helps!
/Mats

[王晋强]

hi Mats,

would you please send me the Dell driver you collected? we can give it a try on a Dell 2950 server and that would be very helpful in locating the problem.

Thanks,

Andy

[Mats Brodin]

Hi Andy
Here is the "driverpool" from the DELL server in 7z format, cause Google does not allow .zip

Regards
Mats

--
*****************************************************
* Mats Brodin
* mats....@gmail.com
* mobile +46 (0)704 333 799
*****************************************************

[Mats Brodin]

Hi again

Made some more testing:

BMR from a backup to DELL 2950 (original Windows installation) works, Windows 2003 server boots up.
D2D r16 update7
Copied the drivers to a USB stick from this server.

Erased the disk

BMR from a backup of a Virtual server (Windows 2003, 1 CPU) and everything looks good, D2D suggests to inject the PERC raid driver, and I try to manually inject drivers through the Driver utility. (Adaptec SCSI, some USB drivers I can inject)
Choose reboot and the message appears:

Windows could not start because of the following  file is missing or corrupt: <Windows root>\system32\ntoskrnl.exe. Please re-install a copy of the above file.

Did a new test and manually replaced the ntoskrnl.exe from the original Windows 2003 server but the file is the same date and size so it does not help.

Collected the Bare Metal logfiles after the first BMR if you are interested !

Regards
Mats

[王晋强]

Hi Mats,

Sorry for late reply. Can you please help to send me the boot.ini file on both the original VM and on the target 2950 server after BMR? you can get it by booting the server up using BMR ISO. You can find it under root directory of C: drive. if possible please also send the BMR log files to jinq...@gmail.com.

this might be caused by the boot.ini entry was not properly updated after BMR, it may happen if you have OEM partition in your system. For an  example, if have OEM partition and your OS is installed on C which is the second partition, the boot

Thanks,

Andy