cybis1
asked on
Restoring Symantec system recovery image to Hyper-V machine
I am trying to restore various Symantec system recovery 8.51 images that have been backed up from several different HP proliant servers. During the restore process I am asked for new drivers, but the drivers aren't accepted by the recovery process, and when the virtual machine is restarted after the restore I get a Blue screen of death. Has anyone any ideas on how to get this restore process working.
Some background:
VSERVER
The machine I am trying to restore onto is an ML350G5, with twin XEON E5420 quad core 64bit processors, 16GB RAM, HP Smart Array controller E200i. Running Windows server 2008, and Hyper-V. The settings in the server BIOS are as directed by HP, and in fact I couldn't initially get Hyper_v to run before I had changed these settings. Hyper-V does now run. I have called this VSERVER.
SERVER1
One of the machines I am trying to restore is an identical ML350G5 server with the E200I array controller.
SERVER2
is an older ML350G4, with an HP Smart UltraSCSI RAID controller, 4GB RAM
PServer is an ML110 G5 server with a built in SATA RAID controller configured as RAID1.
Recovery Process:
I have set the virtual machine to boot from the system recovery boot CD, which boots fine, then point the recovery image to one of the backups, also choosing the options to prompt for new drivers.
During the end phase, the recovery process asks for two drivers:
one is IDE\DiskVirtual_HD________
The other driver is PCI\VEN_8086DEV_711SUBSYS_
Description: Intel Corporation, 82371AB/EB/MB PIIX4/E/M EIDE Controller
(this intel driver seems a bit strange as it is quite an old driver, and as far as I can tell isn't on any of these servers)
Anyway I'm not sure where I can find the Virtual HD driver, but I have searched the Intel website for the 82371 driver, and extracted the inf file, but the option screen asking for the driver says it is the incorrect one.
I have also created a new recovery CD with this driver incorporated in it, but still no luck.
The strange thing to me is that one of the servers (SERVER1) is using the identical E200I array controller as the host machine (VSERVER), and no IDE devices, so why am I being asked for an old EIDE driver?
A bit long winded but I wanted to give as much information as possible.
Has anyone any ideas on how to get this restore process working.
Thanks
John
bsod.png
virtual-hd.png
intel-driver-required.png
virtual-Machine-settings.png
Some background:
VSERVER
The machine I am trying to restore onto is an ML350G5, with twin XEON E5420 quad core 64bit processors, 16GB RAM, HP Smart Array controller E200i. Running Windows server 2008, and Hyper-V. The settings in the server BIOS are as directed by HP, and in fact I couldn't initially get Hyper_v to run before I had changed these settings. Hyper-V does now run. I have called this VSERVER.
SERVER1
One of the machines I am trying to restore is an identical ML350G5 server with the E200I array controller.
SERVER2
is an older ML350G4, with an HP Smart UltraSCSI RAID controller, 4GB RAM
PServer is an ML110 G5 server with a built in SATA RAID controller configured as RAID1.
Recovery Process:
I have set the virtual machine to boot from the system recovery boot CD, which boots fine, then point the recovery image to one of the backups, also choosing the options to prompt for new drivers.
During the end phase, the recovery process asks for two drivers:
one is IDE\DiskVirtual_HD________
The other driver is PCI\VEN_8086DEV_711SUBSYS_
Description: Intel Corporation, 82371AB/EB/MB PIIX4/E/M EIDE Controller
(this intel driver seems a bit strange as it is quite an old driver, and as far as I can tell isn't on any of these servers)
Anyway I'm not sure where I can find the Virtual HD driver, but I have searched the Intel website for the 82371 driver, and extracted the inf file, but the option screen asking for the driver says it is the incorrect one.
I have also created a new recovery CD with this driver incorporated in it, but still no luck.
The strange thing to me is that one of the servers (SERVER1) is using the identical E200I array controller as the host machine (VSERVER), and no IDE devices, so why am I being asked for an old EIDE driver?
A bit long winded but I wanted to give as much information as possible.
Has anyone any ideas on how to get this restore process working.
Thanks
John
bsod.png
virtual-hd.png
intel-driver-required.png
virtual-Machine-settings.png
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I would recommend that when you're using the SRD you may want to load Microsoft's scsi adapter driver as the storage driver, this may help. See if you can get .flp file (floppy image) to make it easier to load
ASKER
Thanks, i'll give this a go tonight and let you know.
If we were to change to ESX/ESXi from Hyper-V what is the difference between the two? ans which would be better for a diaster recovery senario of running 3 x virtal servers on one "big" machine?
If we were to change to ESX/ESXi from Hyper-V what is the difference between the two? ans which would be better for a diaster recovery senario of running 3 x virtal servers on one "big" machine?
ESXi is free and is good for stand alone. If you want DR I would go with ESX Foundation which allows you High Availability and VMotion (allows the VMs to boot from a different ESX host if one goes does but requires shared storage and vmotion allows you to move VMs realtime between hosts without downtime).
ESX/ESXi has a much smaller footprint and gives you more resources to run your virtual machines. It also gives you more flexibility in OS installations, running many flavors of Linux, Solaris, as well as Windows.
ESX/ESXi has a much smaller footprint and gives you more resources to run your virtual machines. It also gives you more flexibility in OS installations, running many flavors of Linux, Solaris, as well as Windows.
ASKER
Sorry about taking ages to reply. I have nw tried the restoring using esxi server. Much easier and it just works.
Thanks for your suggestion.
Thanks for your suggestion.
ASKER
Thanks for the advice
ASKER
I am trying option 1, configuring the Virtual machine to boot from thr SRD, and then restore anywhere to a new VHD..
I have tried the other way too, converting the backup image to a vhd, but that was the same result, as BSOD.
Thanks.