Having trouble opening .tib file on Windows 10
I've not tried to open a .tib file (created with ATI 2017 under Windows 7) with Windows 10 before. I've now tried several times and am stuck. When I click on the .tib file to open it, I enter the encryption key, as expected, but instead of seeing an explorer-like window with my backed up files and folder, I get a "Locate the volume with number '1':" window showing This PC > Documents (see image). I have no idea what to do with this. Ideas?
BTW - this "Locate the volume ..." dialog cannot be closed or canceled. It pops right back up again. You have to log out for it to go away.
later ...
I then tried opening this .tib on Windows 7 and the same thing happened! What does this mean? A corrupt .tib?
Allegato | Dimensione |
---|---|
ATIlocateTheVolumeWin10.png | 38.28 KB |


- Accedi per poter commentare

I tried several of the incrementals and all gave me that weirdness. I went back to the full back up and that worked fine. Fortunately, it wasn't that old.
Not to sound like a newbie, but how do I "validate" a .tib file? I'm just opening it via Windows Explorer, not booting from the recovery DVD. I don't see a validation tool.
- Accedi per poter commentare

Right-click on the .tib file in Explorer, then on Acronis True Image, then on Validate.
Note: slightly different options shown if doing this for a .tibx file. (no Mount option)
- Accedi per poter commentare

Steve - thanks! I've recorded that as a "tip". I've tried this on both the incrementals from my backup and the full backup. What is supposed to happen? When I click on 'Validate' I get a spinner for a moment, then nothing. Does nothing mean "valid"?
- Accedi per poter commentare

Clicking on Validate in Explorer should cause a validation operation to start in the main ATI GUI for the task that created the file, or else if that task isn't present, a new task using the name of the .tib file.
- Accedi per poter commentare

As I OK restored from the full backup which was made only a few days days before the incrementals, I've not tried your validation suggestions. I'll keep that for future reference.
- Accedi per poter commentare

I'm having the same issue with trying to open my incremental files (see attached pics). Validation fails on all incremental files. I can open/browse the Full file. I have the entire chain, so I'm still not understanding why I cannot access the incremental files.
Allegato | Dimensione |
---|---|
538191-184640.png | 109.96 KB |
538191-184642.png | 24.28 KB |
- Accedi per poter commentare

Scott, what happens if you double-click on any of your incremental files? Does it open and show you the contents?
Is your F: drive location on your local computer or is it a mapped windows drive to a network location?
The error message is not referring to a specific file but to a generic one with @task@ in the name which is normally only used within the task script file, so strange that this is being given here?
- Accedi per poter commentare

Hey, Steve. I get that same message, "Locate the volume with number '1':". I cannot close it... I can only Stop Task in Task Manager. Something that came to mind here... is it possible that all incremental files have been corrupted somehow as they don't validate, and receiving that message is coincidence?
- Accedi per poter commentare

Scott, couple of further questions to ask:
Your image shows the version chain: HAF922OS_full_b81_s1_v1 and associated incremental files down to HAF922OS_inc_b81_s13_v1. Are there any other version chains or incremental files for the b81 chain?
How did the earlier version chains get deleted? b80, b79, etc?
Was this done manually outside of the ATI GUI by using Explorer?
If you have manually deleted older version chain files, then this leaves behind information about the deleted files in the internal database files used by ATI which will give these error messages!
The simplest method to resolve the above if true is to force a rebuild of the database as per the steps given in KB 60915: Acronis True Image: repairing program settings
- Accedi per poter commentare

Looks a rebuild is in order, as I did manually delete the last chain. I don't normally do that, but was cleaning up the drive. I did not realize the chains were connected as such.
- Accedi per poter commentare