Salta al contenuto principale

File recovery failed "due to an error" -- no further information

Thread solved

I have a backup of certain directories on my Windows 7 desktop PC (a few thousand files totalling about 481 GB), and the backup is saved to an external HDD (in .tib format). I recently tried to recover this backup to a new hard drive and found something strange, the recovery reported as failed "due to an error" and provides no further information about what that means, yet when I look in the recovered folders, they appear to be recovered regardless? Granted I haven't done an exhaustive scan to check if all files are accounted for, so it's possible something has gotten lost and I don't know what. I find it a little frustrating that Acronis reports this failure message but without any more specifics or more granular data bout what was recovered and what was not.

I've attached a screenshot of the activity log for the backup and recovery. As you can see, the backup was completed and validated with 481.6 GB of data on 7/31. Today when I tried to recover the files to their original destination, it "failed due to an error", so I tried it again, and it failed again. To check if there was a problem with the backup files I tried validating them again, which succeeded. I then did a test recovery of only a small portion of the files to a different directory than the original ("D:\test"), which succeeded. I then did a 3rd test of the same subset of files to the original location, and it again "failed" -- but despite the error messages, when I look in the folders, they appear to have all the files at least judging by a quick scan (there are thousands of files included). Also after each recovery attempt Acronis said it needed to reboot my system (I don't know why, none of these were protected OS files), and so I let it, and that final recovery step appeared to be successful.

I'm not sure what to make of this. I'd really like some way of confirming if the thousands of files are all accounted for in the recovery, but without a full list I don't know how to verify that. Is there any way to dig into what the error is that Acronis is reporting?

Allegato Dimensione
AcronisRecovery.PNG 41.94 KB
0 Users found this helpful

Theodore, I assume this is a File and Folders style backup.

You could look at the logs created by True Image. Download the MVP Assistant (link in my signature), and open the Log Viewer portion. The Demon logs may give an indication.

I'm guessing a problem that may have affected a subset of files and could be related to permissions in the original folders. I don't know if any of those folders were part of Windows or strictly user folders. Could your anti-virus be preventing a write? More info needed.

 

Thanks very much for the tip BrunoC, I was able to download MVP Assistant and use it to inspect the logs. The logs revealed an error like this one for a few select files from the backup:

8/19/2021 09:27:34:666 AM -07:00 6228 W00000418: Error 0x418: File 'D:\GAMES\Call of Juarez\jre\lib\fonts\LucidaTypewriterRegular.ttf' is inaccessible at the moment. There will be an attempt to recover the file on reboot.
8/19/2021 09:27:34:728 AM -07:00 6228 I000A03ED: Preparing for Windows reboot...
8/19/2021 09:27:34:786 AM -07:00 6228 I000A03EC: Rebooting Windows. The operations will be performed before the system starts...

And yet after the reboot, Acronis had still marked the operation as unsuccessful. Weirdly though, when I looked at the folder that the problematic files should have been restored to -- they were actually present and appeared to be valid. So I'm not sure why Acronis said that it was unable to restore those files from the backup; it's possible that something about the files from the original disk were corrupted (the hard drive I was backing up from was dying, hence the need to do this backup/restore). In any case, I again tried a restore operation but deselected the identified problematic files, and at that point Acronis was able to complete the operation successfully. So that answers my question and the bad files in question are apparently still restorable, so that solves my problem. Thanks again. That tool is impressively detailed and it's a wonder to me it isn't included in Acronis officially.