Validation problem: Falied to open backup
I have observed a strange behaviour which I'd like to share with you guys.
If it is not a bug for sure it is a big inconvienence.
The excersise is a subset of my bigger battle with Acronis and I learned that communicating with their support cost too much time and giving a very little in return. So I try the forum now. I'd be interested what do you think about that:
So, what I did was:
- On computer A I created a partition backup and save it on the pendrive F:\ to the file xxx.tib
- I generated a bunch of checksums for the xxx.tib file and I also triggered Acronis validation of the xxx.tib file which passed
- I unplugged the pendrive and I plugged to second computer, let say computer B. On computer B I copied the xxx.tib file from the pendrive to the network drive mapped. The location of the xxx.tib file on computer B was V:\BCKP\COMP\JUL\xxx.tib. V:\BCKP\COMP\JUL folder was empty prior the copying.
- I genererated the same bunch of checksums as in step 2. They were EXACLTY THE SAME. File size - I know, I don't have to mention it here, but to be 101% clear - it was the same.
- In Win Explorer on the computer B I right clicked file xxx.tib in location V:\BCKP\COMP\JUL and from this Acronis True Image context menu I triggered the validation action in the result I've received the message:
"Failed to open backup V:\BCKP\COMP\JUL\xxx.tib. Make sure the backup location is accessible and contains all versions of the backup.
If you moved or renamed it return to the same location or restore the initial file name, then click Retry. If you dele it, click Ignore to create a new backup version."
My questions now:
- OK, I did change the location, but this is quite common scenario that, in restore operations, the backup file location is seen as a different from the hardware ran under Acronis Rescue Media during the restore operation, comparing to that what had been seen during the backup operation. Why ATIH has a problem with opening the its own backup?? The xxx.tib is 100% accessible on the OS level
- Is it failed to open because V:\ is the network drive? Well, again, it is quite common that a user store these huge backup files somewhere in the network.
- And, foremost, I don't want to restore. I just wanted to check validity of the backup. Why location of the backup file has an impack on the result of the validation?
- And last but not least. In the message window of the message I quited above in point 5. There is no Ignore button.
Is it really the intended behavior?
Misc:
- I used a name of xxx.tib as a short version of the real, default ATIH tib file name. I did't touch the oryginal file name it at all.
- Both computers have Win7SP1x64 and Acronis version 2019 Build 14690
Enchantech wrote:(...)
If you wish to move a .tib file from its original location (...) you need to do so using the True Image application as doing it with any other method causes the backup database tracking to become corrupted and in turn will generate errors like you mention here.
(...)
Where is the database you mentioning here?
Enchantech wrote:(...)So you moved the .tib file to a second computer different from that which the backup file was created then accessed the file via Explorer on this second computer. So why the problem? Answer is that the task that created the backup doe not reside on the computer being used to perform the task specified by the user (validate in this case). Without that task available to True Image on the second computer there is no database record of the backup so you generate an error.
Again, what database you are talking about here? Where it sits?
My expectation is the tib file, as any form of backup, shouldn't have ANY dependencies stored in itself which could affect the its validation. There is no reason, no value added by doing so. The tib file Itself, regardles the location from under which it is validated or restored from, should contain all and enough information for successful performance either of these operations.
The database is found at C:\ProgramData\Acronis\TrueImageHome\Database and is a SQLite DB but should not be edited or changed.
Issues can arise when the name of the backup image file(s) being validated matches with information held in the database for another task, when a mismatch between information held in the database and the location of the files can cause errors.
When you select Validation for a .tib file from Explorer, this then results in a new entry in the ATI GUI under the 'Others' section. The status of the validation is then shown in the GUI as you would see for a Backup action.
I was able to validate backup .tib files held on an external drive and on my NAS, both of which were not created on the same computer and had never been referenced in the database or registered as tasks shown previously in the GUI.
If needed, validation can also be performed completely offline from Windows by booting from the Acronis Rescue Media, where the database is not used or known.
MimiKLM wrote:My expectation is the tib file, as any form of backup, shouldn't have ANY dependencies stored in itself which could affect the its validation. There is no reason, no value added by doing so. The tib file Itself, regardles the location from under which it is validated or restored from, should contain all and enough information for successful performance either of these operations.
In theory, you are correct that the .tib files alone contain all the information needed for a recovery or validation. As Steve said, a recovery or validation done by a stand-alone recovery medium does not have access to this database and can perform the requested activity without trouble.
However, I think there is added value to the action taken by ATI. My assumption is that a validation done from within ATI is validating more than just the .tib files. It's validating the backup and recovery configuration. If the contents of the .tib files and the content of the database are in conflict, then configuration backed up may not match the configuration to be restored. This might be just what you want, but it also might represent a very serious error. ATI cannot know which.
I suppose you could suggest to Acronis (via Feedback) that they include a mini-validation that does not cross reference the .tib files and the database (or does the cross reference but issue just warning messages).
The responses to this thread have spread to new lengths. I can confirm that Validation can be run successfully on backup files created on PC A from PC B. Having said that I believe this depends on if the backup file is:
- A - a full version backup.
- B - an incremental version backup as long as all versions of the backup chain are present and available.
- C - a differential backup.
The error message in the OP suggest that an incremental version backup was chosen in this example and not all versions of the backup were available when the validation was run.
If the above is not true then I suspect the backup was somehow corrupted during the moving process or the media on which the backup is located was corrupted to begin with.
I also believe that full and differential version backups in a like example could be validated successfully unless corruption has occurred.
Select add existing backup. Select the *.tib file. Select validate