Skip to main content

Recovery fails if another backup location is not available

Thread needs solution
Beginner
Posts: 2
Comments: 3

I have backups like this:

B1 -> X-Network-Loc
B2 -> Y-Network-Loc

At this moment Y-Network-Loc is not accessible.

Now if I try to recover B1, True Image prompts me for credentials for Y-Network-Loc, which is not available, and hence fails to connect, and my B1 recovery fails with:

"Failed to check last versions of backup"

How to get around this? I don't care about B2 or its location.

I have even removed the B2 settings.

0 Users found this helpful
Legend
Posts: 99
Comments: 21367

#1

Sandeep, welcome to these public User Forums.

Information about backup tasks, file locations etc are held in an internal database used by the Windows ATI application, so if your backup tasks are causing the issue you describe it is probaby because you are attempting a recovery from within Windows.

If you boot from the Acronis rescue media and attempt the recovery, then unless you have changed backup destination locations within the same backup task, this issue should not happen as the rescue media does not need or use the database information.

Beginner
Posts: 2
Comments: 3

#2

Thanks for the reply.

I just need to restore a few files. I should not have to go to rescue for that.

Is there a way to cleanup the internal locations?

 

Overall, one backup affecting the recovery of another backup is a pretty bad behaviour.

Legend
Posts: 99
Comments: 21367

#3

Try doing a Validation for the backup with the files you are wanting to recover, if it throws up errors for files in the other network location, take the Ignore option if available.

Alternatively, try double-clicking on the .tib file in Explorer and let it open and then see if you can use normal copy & paste commands to get to the files you want?