Skip to main content

using Universal Restire

Thread needs solution

Hi Everyone,

I am desperately trying to work out how to use Universal Restore with ATI 2017. 

What I'm trying to do is use a backup image created with ATI 12 to a dissimilar hardware configuration (new SSD size; 250 GB to 500 GB).  So far I have had no success so assume it is something that i'm doing that is not correct.  I've read the KB articles and all the help files available but cannot achieve success.

Any help and advice would be greatly appreciated.

Thanks and regards

Roy Bailey

 

 

0 Users found this helpful

Roy,

Your changing from a smaller to larger disk drive would not be considered a change to dissimilar hardware.  Therefore using Universal Restore is not necessary.  You say that you are attempting to use an image created with ATI 2012 I believe and using ATI 2017 to do so, this may be a problem but give it a try anyways.  Just use the bootable recovery media to restore the image to the drive and see if it will boot without running universal restore.

According to Backup Archive Compatibility Across Different Product Versions | Knowledge Base

TI 2017 is not comptibile with TI 2012 archives, 2015 is.

Thank you Enchantech and Thomasjk for your responses.

Firstly Enchantech: i have read somewhere that changing to a larger HDD or SSD causes the HAL to change.  Cannot recall where.  

I have used both bootable media created by ATI 12 and ATI 2017 to restore the image and the boot fails.  Please see my response to Thomasjk regarding 2017 restore.

Do the restored partions and the original partition have to be exactly the same size?  One thing I failed to mention is that the original SSD that crashed was a RAID 0 configuration. Is that significant?

Secondly, Thomasjk: You are correct that ATI 2017 is not compatible with ATI 12 archives.  When I tried, the restore failed at the very end.

I shall persevere and hope to find a solution quickly.  More reading required.  Re-installing the OS (W 10 updated W 7) and all the programmes will be a real pain.

Thanks again,

Roy

My apologies to both of you.  I'm using ATI 13 not 12 as stated in the about posts.

Thanks,

Roy

Roy...

Couple of things to be sure:

1) How you boot the recovery media determines the partition scheme during the recovery process.  I'm assuming any machine you used with 2012/2013 was most likely a legacy/bios OS install.  So, on your new machine, you'll need to make sure teh bios is configured to boot the recovery media (especially if using 2016/2017 recovery media) in legacy mode as well and not UEFI.  Otherwise, if you boot it in UEFI, it will try to convert the recovered image to UEFI/GPT and that could cause issues.

2) In the bios, teh SATA mode must be the same on both systems.  So if the old system was using IDE and the new system only has AHCI or RAID, this will be a problem.  If the old one was SATA and the new system is currently set to RAID this will also be a problem.  Make sure the bios SATA mode is the same as the old system.  As you said the old system was a RAID 0, then you need to make sure the system is RAID now too and not AHCI.

3) The old system was in RAID 0 so you had a RAID controller installed with drivers for that particular controller - this is most likely the sticking point on the new system.  Even though you are using universal restore, but because you must have the SATA mode set as RAID, you may need to inject the RAID controller drivers for your new system as well.  At a minimum, you probably need the Intel IRST drivers loaded with universal restore, but depending on your motherboard, you may have specific RAID drivers needed as well. 

Hi Bobbo_3C0X1,

Thanks for the advice.  Quite a lot to digest.  I am almost at the point where giving up trying to restore the original image and reloading W 7, then updating to W 10 and reloading all other programmes will be quicker and easier than trying to work through this problem.  Why I'm reluctant to proceed down the path of a complete reload is that I had great difficulty in updating to W 10.  Had to uninstall Avast Premier, Malwarebytes and Superantispyware incrementally to find out what was stopping the upgrade and when the upgrade was successful, re-install the protection software.  A real pain but we succeeded.

Also, I have no idea what SSD drivers were installed in the original installation as the SSD crashed completely beyond recovery.

Thanks for the help.  I shall make my decision on which path to go down later today and will post the results when everything is sorted.

Roy.

Sorry to hear about your system woes.  

In the long run, if it we're me, I'd probably bite the bullet and start fresh with Windows 10 (actually, that's what I did too - but, by choice). Starting fresh with a new OS can save a lot of time and headaches down the road, even though it can be a pain up front.  I really like Windows 10 though and have been very happy with it - even when I upgraded from Windows 10 to the recent Windows 10 anniversary update.  Microsoft has us all fooled though - none of these Windows 10 "upgrades" are really upgrades - they're full blown OS installs that port the data, settings and applications over after the install is complete.  In most cases, this works well, but can still lead to problems for some.  

If/when you clean install, takes some backups along the way.  For me, I usually get Windows setup (settings, patches, etc) "as is" with just windows and nothign else and take a "base image".  I then install all of my 3rd party apps and configure those and take a second "base image".  I then import my data files (documents, music, pics, et) and take a final base image.  That way, if I ever need/want to start fresh, I have some options to work with to save some time down the road.  Although, if things do get really screwy at some point, chances are there will be a newer Windows 10 version to start fresh with then anyway.

 

Hi Bobbo_3COX1,

Sorry about the delayed response but have been busy re-installing my OS and applications software.

Personnaly I'm not impressed with W 10 especially with all the information that is sent back to M/S without one's knowledge or consent.  That has been dealt with by using DoNotSpy10.

As far as ATI 2017 is concerned it is my opinion that Acronis have ignored the KISS (Keep It Simple Stupid) principle. The interface is not as intuitive as earlier versions and I have un-installed it and gone back to ATI 13. Wasted my money on the upgrade, never mind.

Once all is installed and stable (problems with applications freezing at the moment) I shall clone the SSD which I feel is a quicker method of creating a back up facility.

Thank you everyone for the help and advice.

Roy