Acronis True Image Universal Restore – Problems
Acronis has produced a breakthrough enterprise (well not quite yet) backup and imaging product at a fraction of the cost of those big vendors. Their imaging product has been very successful. With all the buzz about dissimilar hardware recovery, I was thinking how sweet it will be when disaster strike where I can recover all my OS, configurations and applications into brand new hardware with different model within just a few mouse clicks. This dissimilar technology supposedly give us the administrator peace of mind without worrying even on different vendors like Dell vs. HP vs. Compaq vs etc. Contemplated of what this magical software can provide, I ’stood in line’ and ‘jump into the band wagon’ to test it out. Boy O boy… was I wrong. Although the process is extremely simple and straight forward however the most time consuming part is dealing with restored OS. It would either go to constant boot loop or BSOD.
I also tried Symantec System Recovery, a very similar concept with Acronis. It was nicely done and I can reboot my OS into dissimilar hardware (from Dell 1950 to 2950). The server boot up normally, however it generated whole bunch of errors in the event log. Because this is a production server, I wouldn’t want to risk it so I rebuilt the server from scratch at the end. Back to Acronis, despite the love / hate feelings about this product, I decided to write this up and hopefully this will benefit some.
In order for it to work (at least in my case here), just follow these instructions and screen shots.
Prerequisites/ Checklist:
1. Make sure you have up-to-date build of Acronis software. If not please download it. The latest I am using as of this article is #8206.
2. You have created the Acronis boot Disk (with Universal Restore) from the latest build.
3. You have a working copy of .tib file (image file). Verify by browsing it through windows explorer and you will be able to see the content.
4. You have downloaded the latest version of mass device storage drivers from the manufacturer or vendor website.
5. Make sure you have downloaded the correct driver and in order to find the correct driver, the best way is to get it from the BIOS screen when your server is booting up.
6. You MUST have the HAL drivers. I am not sure why Acronis does not include this or maybe it is not loaded properly, the HAL drivers are supposed to provide that Universal Restore function which ultimately tranparent to OS regardless of the underlying hardware used. That is also most probably the reason why many the same blue screen of death and the boot constantly on the loop failing to load the common HAL.
Acronis Universal Restore Wizard
Now that you have the pre-requisites covered. Let’s look at each of the screen shots and follow through:
a. Clean up your RAID. Depending on your vendors, you may need to initialize the RAID subsystem using the BIOS screen. Below are shots from DELL’s PowerEdge Expandable RAID Controller (PERC 5i Integrated) BIOS.
Quit configuration utility and Ctrl+Alt+Del to reboot the server.
b. Insert Acronis boot disk and plug in your USB drive that holds the image (.tib) file.
You will get this options if you have not performed the RAID cleanup stated above.
Since you have picked the entire drive, just select No.
This is important piece, select use Universal Restore
Click Add and load HAL.inf, Acronis will then show all the drivers.
This is the second most important step, click Add and select the RAID driver FOLDER.
Optional: Select auto reboot when done, remember to remove the boot disk when the restore begins.
Review the summary and click Proceed.
Restore process will take quite fast and the time shown is quite accurate. Depending on your data and server performance, the time varies.
Typical error: PCIVEN_1028&DEV_0015&SUBSYS_1F031028&REV_00 If incorrect RAID driver was loaded or the driver was not found, you will get this. You still have chance to load it if you have the correct .inf and its associated files available.
You will get this once the restored process has been successfully completed.
If everything runs smoothly you will find you are on your way to recovery with much less effort. The time for recovery it’s worth the money during disaster. One last few steps you would want to check is review all Windows event Logs, check services, perform test on applications and you will be prompt (in my case) to load RAID driver. Just load it one more time and restart.
Below is a comparison of system info of what was original system (Dell PE2970) vs. the restored (Dell PE1950). In RED is the restored system. It was from RAID-1, RAID5 system to RAID-1 restored system with different CPU and memory size.
OS Name Microsoft(R) Windows(R) Server 2003 Standard x64 Edition
Version 5.2.3790 Service Pack 2 Build 3790
Other OS Description R2
OS Manufacturer Microsoft Corporation
System Name DC1
System Manufacturer Dell Inc.
System Model PowerEdge 2970 1950
System Type x64-based PC
Processor AMD64 EM64T Family 16 15 Model 2 6 Stepping 3 AuthenticAMD ~22944 GenuineIntel ~3193 Mhz
Processor AMD64 EM64T Family 16 15 Model 2 6 Stepping 3 AuthenticAMD ~22944 GenuineIntel ~3193 Mhz
Processor AMD64 EM64T Family 16 15 Model 2 6 Stepping 3 AuthenticAMD ~22944 GenuineIntel ~3193 Mhz
Processor AMD64 EM64T Family 16 15 Model 2 6 Stepping 3 AuthenticAMD ~22944 GenuineIntel ~3193 Mhz
BIOS Version/Date Dell Inc. 3.0.2, 9/26/2008 2.5.0, 9/12/2008
SMBIOS Version 2.4 2.5
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume2
Locale United States
Hardware Abstraction Layer Version = “5.2.3790.3959 (srv03_sp2_rtm.070216-1710)”
User Name DOMAIN\Administrator
Time Zone Eastern Daylight Time
Total Physical Memory 8,186.07 4,090.64 MB
Available Physical Memory 6.59 3.16 GB
Total Virtual Memory 9.56 5.74 GB
Available Virtual Memory 8.45 4.98 GB
Page File Space 2.00 GB
Page File C:\pagefile.sys
I hope this is an useful article.
Update:
This pdf, System Migration to Different Hardware PC, is provided by Acronis support. Check it out.
Great post!!
Where do I get HAL drivers??
Tnx
Vico
You can grab it and its associated files from the i386 folder.
Thank you. The Universal Imaging Utility has been doing this for 5 years and has worked out the issues with quirky devices, drive types, HALs, drivers and so on. It works with any imaging tool.
Is your imaging solution incorporate the latest scsi or mass storage drivers from major vendors or do we need to load it manually?
Yes, it does. This database is maintained and updated by the developer and you receive them through the AutoUpdate feature.
Hi
i tried all the above with no succsess…
at the end it worked very simmple, it took me about 4 Days (grr).
Universal restore took all needed drivers from the before copied data.
section: windows/system32/drivers (pointer was just set to the windows directory)
even the hal drivers were taken from there…
alternative: extract the windows directory from the Image to a disk or directory and set the search pointer to this…
I recovered a w2003 SP2 with SQL from a 4 Proc Server down to a
Pentium 3 , single Proc, machine….
Having the right SP Files is a key, I guess
regards
Thomas
Hi Thomas, thanks for sharing your experience. I can understand how frustrating at times when you need it up and running.
When you said ‘pointer was set to windows directory’, which page were you specifying it? Is it the first mass storage device page or the second one (where you have options)? Chee
Hi Chee,
Where the HAL drivers were specified i did not set anything,
on the next page I just set the pointer (add search at…with both check
boxes activated) to the ?:\windows\ directory I extracted from the image
onto a external usb disk.
I think when the new hardware has standrad components which are already
included in the windows OS disk it is a question of having the right service
pack version to be obtained from universal restore…,mostly any microsoft
CD is not at the latest service pack level installed on an active machine
I am just playing around with it, giving universal restore a hard time to
restore from very new Quad proc. servers to an old P3 DELL System with an
old Perc3 Raid…
But ist taking time time….
Best regards from Germany
Thomas
That could be true. The product itself is not so consistent although most of the time it will eventually work. I read forums and many others have different experience. I wish Acronis will have more specific answer to this.
Chee
Please help. I am using Acronis Echo and UR to restore an image from a Dell 2650 to a Dell 2950. I specify the new mass storage device on the Dell 2950 (Perc 5/i) during the restore. Right at the end, Acronis and UR ask for ACPI. I skip that driver. The Dell 2950 boot and that works fine. The dell 2950 boots into Windows, but then it started to as for drivers for PCI bridge and all sorts. I compare that System Drivers from the restored 2950 to a clean install 2950, and they look different, especially the Intel 5000x chipset drivers. And Dell does not have a chipset driver for the 2950.
I thin Thomas’s solution may help me. Would the following work?
1. On the Dell 2950 with a clean OS install, boot in Acronis. Take an File backup of \WINNT, which also includes System32\Drivers and \INF
2. Restore \WINNT to an USB disk. Say it is U:\WINNT.
3. On another Dell 2950, restore the Dell 2650 image to the 2950, but on the second page of UR, check both Search boxes, and add the U:\WINNT path.
I have used Driver Genius to backup the drivers from the clean install 2950, and restore them into the 2950 with the 2650 image. But that 2950 did not get past the login screen.
Thanks in advance.
BTW, the Dell 2950 with a clean install OS was built with the Dell build DVD.
Calvin
Hi Calvin
1) I connected my streaming device (HP SDLT 320) to the internal SCSI Controler not to the PERC
2) from the Image of the original machine I extracted parts of the windows directory (drivers, system32, inf, etc.) to an external USB disk, you may extract it completly. Do not use a windows CD as it not have the latest SP’s. You can ceate also a (work) partition on the SCSI Raid an put the extracted windows (WINNT) directory there.
3) reboot machine with acronis Universal restore
…
4) When it comes to the first “select driver screen” do not select anything
5) On the second screen where you can select a path or directory set it to the USB Disk or work partition where the extracted windir is present (windows or winnt) do not set path on subdirs in the windir
6) select both checkboxes in this screen
…
Go for it
you may also check ACPI Support in the BIOS is it set it on or of
If this does not help anyway you may boot from windows OS CD and recover the found windows, but this takes a long time an means reinstall all SP drivers…nasty
Please Let me know if this was working
Mit freundlichen Grüßen
Thomas Pahlings
Computer Brokers e.K.
Sonnenhang 35
D-63667 Nidda
Tel.: +49 (0) 6043/985200
Fax: +49 (0) 6043/985202
Mob.:+49 (0) 171/8110099
email: thomas.pahlings@computer-brokers.de
www: http://www.computer-brokers.de
One more thing,
I think universal restore checks the new machine like windows does when you install, when it misses a driver try to give it to UR from a windows CD if possible but after it has collected all the other drivers from the extracted windir
Thomas, I think you can read Calvin's result here.
I just found out when researching the driver for the chipset.
Universal Restore from Dell PE 2650 to Dell PE 2950
At some point I am thinking Calvin's solution takes a lot effort and requires additional similar hardware. That, sort of defeat the purpose of having Acronis UR.
Chee
Thomas, I think you can read Calvin's result here.
I just found out when researching the driver for the chipset.
Universal Restore from Dell PE 2650 to Dell PE 2950 http://www.wilderssecurity.com/showthread.php?t=2...
At some point I am thinking Calvin's solution takes a lot effort and requires additional similar hardware. That, sort of defeat the purpose of having Acronis UR.
Chee
Chee, Thomas, sorry for being a daft, but I still do not get the concept.
As Chee had described above, I can achieve restoring a Dell 2650 image into a Dell 2950. But my way is long and complicated. I guess I am using the hard way to achieve restore to dissimilar hardware only because I do not understand how UR works. I thought that UR can only help you to install the mass storage adapter driver for the new hardware. Once the OS boots on the new hardware, then I would manually reinstall the new drivers.
But it sounds like what Thomas and you are describing is that UR can also be used to inject in all the new drivers right? If that is the case, then I do not understand Thomas's step 2 where he is injecting the drivers from the directory taken from the image of the old hardware.
Whereas would it not make more sense to backup the drivers from the new hardware and during UR restore, point to the directory where all the new drivers are, not the old drivers from the old machine.
I am still try to figure how this whole process works. Thanks for you patience.
Calvin
Hi Calvin, what is your long and complicated way? Personally I do not speak for Acronis but my understanding (in fact most of us were sold) that UR will automate the restore from one hardware to another without requiring much effort provided that the drivers for mass storage are there. Most of the time it's not with new hardware and there is when injecting new drivers are necessary.
It makes sense only if you are willing to take additional time to setup a new hardware and copy all the drivers. For most of us, we wanted a direct restore to brand new hardware (without OS). The key is saving time and effort, but if you want to setup the OS, Service Pack it, and perform all the updates then capture the drivers prior to restore, that is possible but again it sort of defeat the purpose of UR. Don't you think?
Chee
Thanks for explanation. This works for me.
Glad it helps. Chee