Salta al contenuto principale

Cant restore any backup of SSD

Thread needs solution

Hello everybody,

i am new to this forum. I've been using TrueImage for almost 10 years and I've always been happy with it. Due to new computers, I also got a new version, the 2020 version. I always like to make images of my system disk, usually c: (Windows 10)
Unlike my other versions, I cannot restore any single image. Acronis always gets the error "The specified file could not be found" on restart.
My drive that I am backing up is an SSD. Regardless of whether the backup is on the internal HDD or on the HDD in NAS, do I always get the same error?

Who can give me a hint?

Many Thanks

Yo

0 Users found this helpful

Jo, there are various reasons why you might get the 'file cannot be found' error so we need to establish some basic information first.

How are you creating the backup of your SSD drive?
Is this from the main ATI GUI application running in Windows?
Or it is after booting the PC from Acronis Rescue Media?

Where are you storing the backup image for this SSD backup?
Is this stored on an internal drive, external drive, network drive?

If using the main ATI GUI, can you click on the backup task menu (V) and use the menu option to 'Open location' to the destination location, and if so, do you see the backup file?

What file extension is your backup using?
For any new Disks & Partitions backups created in ATI 2020, this should be creating .TIBX files and no files of this type should be deleted using Explorer, especially if you see a small 12KB size .TIBX file as this stores important Metadata for the backup task.

When attempting to do the SSD Restore, how are you doing this?
Starting the restore from within Windows or by booting the PC from Rescue Media?

If you are starting the restore in Windows, then this will require the PC be restarted to launch a temporary Linux based environment for the Recovery, which may not be capable of seeing your backup drive, especially if this is stored on a Network drive location.

If your backup is stored on an encrypted backup drive using such as BitLocker, then again, the restore environment would need to have BitLocker support which the Linux one does not have!

See KB 63226: Acronis True Image 2020: how to create bootable media and KB 59877: Acronis True Image: how to distinguish between UEFI and Legacy BIOS boot modes of Acronis Bootable Media

KB 63295: Acronis True Image 2020: How to restore your computer with WinPE-based or WinRE-based media

Hello Steve,

thanks for the quick feedback.

1. All backups available; i only made full backups (*.tibx)

2. The source of the backups is a 1TB SSD

3. The target is the internal HDD or an HDD on the NAS

4. 10th Generation Intel (R) Core (TM) i7-10700 processor

5. 32 GB (2 x 16 GB) DDR4 2.933 MHz

6. Windows 10 pro

I made a Rescue USB stick with TrueImage. If I boot from this, I can restore the backups. It is noticeable here that the destination (actually C :) is denoted by D :. The backup that I am restoring is on D: But if the backup was successfully restored and the computer restarts, everything is as desired:
C: \ -> restored system from the BE
D: \ -> all data available

Perhaps the solution is because Acronis cannot find or mix up the correct partitions when restoring the BU from Windows ?!

Since I use the backup much more often and this is done quite normally via the app in Windows, I accept restoring using a stick. It's not a perfect solution, and I'm not used to it from Acronis either.

I can't say anything about "normal" file backups because I haven't done this yet.

greeting
Jo

Allegato Dimensione
565589-210625.JPG 1.01 MB

Jo, it is normal that drive letters seen when using the Acronis Rescue Media are often different from those you see in Windows.  This has been the case for as long as I can remember and is documented in the user guide.

KB 1519: Acronis Bootable Media displays wrong drive letters

PC systems have come a very long way since Acronis first developed ATI and provided the option to restore drives from within Windows by restarting into a small Linux kernel OS environment.

KB 58006: Acronis software: NVMe drives in RAID mode are not detected by Linux-based bootable media and Acronis startup recovery manager

KB 46250: Acronis Linux-based Bootable Media: Troubleshooting USB HID Devices Detection Issues

KB 45330: Acronis Bootable Media Does Not Detect HDD, RAID or NIC

KB 45331: Acronis Bootable Media(Linux-based): Troubleshooting NIC Detection

KB 59947: Acronis True Image Linux-based bootable media boots into black screen after selecting any option in the option menu

Thank you, Steve.

But all these links do not solve my problem. It is not possible to restore drive c: (OS) from any full-backups i've made.

Jo, sorry but we need to go back to basics again here and start over with a full step by step description of exactly what you are doing, how doing it etc, with screen images if possible.

There should also be logs created for any restore attempt if using the ATI GUI in Windows, or using the Rescue Media, though the latter have to be captured / saved before leaving that boot environment as are lost otherwise.

I have the same problem, a weekly backup has been created for a year.

Now I need a backup and after more than 2 hours the message "Recovery failed" appears.

I tried the whole thing with 5 different backups and on different SSD hard drives.

Unfortunately, I can no longer recommend ATI.

 

I have the same problem, a weekly backup has been created for a year.

Now I need a backup and after more than 2 hours the message "Recovery failed" appears.

I tried the whole thing with 5 different backups and on different SSD hard drives.

Unfortunately, I can no longer recommend ATI.

 

 

Allegato Dimensione
566744-211290.jpg 231.29 KB

First, many thanks to Steve, who trys to find a solution. But, I spent a lot of money (€ 50) and time in ATI 2020. An application for this value must run as expected. Former versions of ATI do so! 

Maybe, I can help others users with this thread, but I will look for an other, working Backup-Software. I can not longer recommend ATI. Sorry!

As I said before, I just make a full-back-up of SSD Systempartition C: (OS) with default. Everythings goes fine. But restoring the backup fails: first, there is a reboot, ok, ATI starts and after a while there is the error.

 

Allegato Dimensione
566859-211320.pdf 1.67 MB

Jo, earlier in this topic you wrote:

I made a Rescue USB stick with TrueImage. If I boot from this, I can restore the backups. It is noticeable here that the destination (actually C :) is denoted by D :. The backup that I am restoring is on D: But if the backup was successfully restored and the computer restarts, everything is as desired:
C: \ -> restored system from the BE
D: \ -> all data available

Perhaps the solution is because Acronis cannot find or mix up the correct partitions when restoring the BU from Windows ?!

Since I use the backup much more often and this is done quite normally via the app in Windows, I accept restoring using a stick. It's not a perfect solution, and I'm not used to it from Acronis either.

Your latest post and PDF document show that you have an NVMe drive that you are backing up and restoring to, which helps explain why there are issues if you attempt to restore to that drive from the ATI application running in Windows, which then requires a reboot to continue.

As mentioned previously, the reboot from Windows launches a temporary small Linux kernel based environment which simply does not have all the needed device support for some combinations of NVMe drives, especially if operating in RAID mode.  See the further links I posted earlier in this topic about the known limitations of Linux based media.

Hi Steve,

thank you for the answer. But what do you suggest for me to do now?

Greetings

Jo

Hi Jo, do you still need to do a restore of a backup for your SSD, or were you able to do this successfully as per your update posted on Sat, 01/16/2021 - 08:24?

If a restore is still needed, then using your USB Rescue stick to boot the PC to do the restore is the recommended method to use.