Salta al contenuto principale

Attempting restore to Dissimiliar H/W, not booting

Thread needs solution

We use Acronis® True Image Echo Enterprise Server® (build 8,163) on a virtual server. What we want to do is restore that to a Physical server. We made a backup to a USB drive, I boot the Physical server with the CD created by the S/W and restore the C drive. It finished and reboots and I see the Windows 2003 Splash screen for about 1/2 a second and then it reboots and does that over and over again. I can't pay Acronis 300 for support. Is there something simple I'm not doing. The S/W is supposed to be capable of restoring to dissimilar H/W.

Thanks for your help

0 Users found this helpful

I can't pay Acronis 300 for support.

And you don't need to because Echo is not supported anymore. Is there Universal Restore prompt when you restore - did you have UR license when the bootable media was built?

We paid for a UR license but I created the bootable CD from the S/W on the server called create bootable rescue media option. It didn't mention anything there or in the options I see when booting off the CD. All I see are basically backup source and destination options. Am I missing something?

In order to have UR on bootable media you need to have UR installed on the computer where bootable media builder is installed before you build the bootable media. IIRC, in Echo UR shows as a separate item in add/remove programs, if it's not there, you won't gert UR. If there is no UR prompt when you perform recover, it either can't detect OS in archive or the media was build without UR.

It wasn't there so I logged in to our account and downloaded and installed iot on our server. I see now in the media creator section an option for the UR. DO I just need this new CD or do I have to recreate the Image Backup with this installed or can I use the Image I have on the drive?

The complex part is to find the right drivers for the new hardware, the most important of which are hard disk controller and motherboard chipset, in the right format (.sys, .inf, .oem) . Then it should be similar to the process described here http://kb.acronis.com/content/4000 for ABR 10.