Skip to main content

Initiating the recovery process from within ATI 2016 itself (Intel Optane RAID).

Thread needs solution

I recently upgraded to a new desktop with an Intel Optane Hard Drive setup.  After some struggle I managed to create a win PE bootable disc with all the additional drivers needed to see my hard drive.  Basically I used the MVP custom ATI Win PE tool (basic) to infuse the drivers I needed.  The default Intel drivers provided in the MVP tool were not enough, but I did eventually locate all the drivers my system likely needs. I can now see all the source and destination drives I expect when using the bootable media I created.  I have followed the recovery prompts all the way to the proceed button and I think all will now work well.

However, I have another question.  In the past (far more often than not) I would launch the recovery process from within the ATI 2016 application right in Windows.  I can still follow all the recovery prompts there, and all the drives I need are visible (not a surprise since I am still within windows).  I have followed the prompts all the way to the proceed button. However, I am skeptical that such an "in-application" restore will actually work now.

As I understand it, once I hit the proceed button, the PC will restart and will then load Acronis Loader in a Linux environment.  I am guessing that the intended restore will now fail since (outside of Windows) the destination Intel Optane drive will not be able to be seen.  However, this is just my guess and I am sure someone here likely definitively knows.  I'd much prefer to be able to launch the recovery process from within Windows, but perhaps that is a thing of the past for me.  Can someone tell me what will happen if I attempt a recover from within the ATI 2016 application?  Will it work?  Will I get an error?  Will something even worse happen like another drive gets overwritten?  Am I now stuck using bootable media for all restores?

Thanks,

Paul

0 Users found this helpful

Paul, if you need the WinPE Rescue Media with additional injected device drivers in order to see your RAID drives etc, then attempting any restore from within Windows will definitely not work as this will only launch a temporary copy of the default Linux rescue media environment which does not have any of the extra drivers you require.

The key reason why the MVP's recommend not attempting this type of recovery being started from within Windows is that it requires that Acronis must modify your Windows Boot Configuration in order to create and boot from the temporary Linux environment - this is fine if all goes well, but if a problem arises then you can be left with an unbootable system where the Boot Configuration is not reset back to how it needs to be to boot into Windows normally.