Skip to main content

Restore data from a corrupted TIB File

Thread needs solution

Hi.

I was stuipd enough to mix up my hdds and partitioned and formatted a hdd where a tib file was stored.

I was able to recover the file by using testdisk, but now acronis says its corrupted and i am not able to recover or even mount it.

Is there a possibilty to get any data (of the not damaged parts of the image) ?

 

0 Users found this helpful

martipn wrote:

I was stuipd enough to mix up my hdds and partitioned and formatted a hdd where a tib file was stored.

I was able to recover the file by using testdisk, but now acronis says its corrupted and i am not able to recover or even mount it.

Is there a possibilty to get any data (of the not damaged parts of the image) ?

martipn, welcome to these user forums.

Unfortunately, the only people who could even attempt to try to recover any data from your corrupted tib file would be Acronis development, assuming that they have the tools that may be needed to try this.

Have you tried validating the tib file using both the Windows and offline Rescue media versions of the Acronis application?  Was the tib file created by the same version of ATIH that you are trying to open the tib with?  If not, do you have the bootable rescue media for the version that created the tib?

Tried to read from HDD with several Rescue Tools (Testdisc, MultiExtractor, etc...) none of them could restore any data from the tib file...

i also contacted acronis wheter it is possible to send them the hdd or the image so that they could look for data, but acronis does not offer this service...

So, conclusion: I made two stupid mistakes:
Of course the bigesst one was formatting and partitioning the hdd.
And the second one was to use a imagetool with tib file format :)

Goodbye Acronis

martinp, from my experience most of the backup tools tend to use their own container file formats that can only be opened by their own application, so Acronis is not alone in doing this.

The only protection that you can use for these cases of 'finger trouble' where accidents happen and things get deleted, formatted, etc, is to keep backups in more than one location, including offline / disconnected where possible.

Ditto to Steve's last note.  Each backup product I have used and/or tested has it's own proprietary backup container so you're stuck with that application for recovering data from it.  Acronis uses ".tib",  Macrium uses ".mrimg", Windows uses ".vhdx", Aomei uses ".afi", Retrospect use ".rdb" etc etc etc. 

Ultimately, having redundancy of backups and/or even backup types/products is your fail safe.  The industry standard (rule of thumb) for IT offices is to use the 3-2-1 backup method and you'll find this on just about every backup products website as a minimum recommendation.

3 sets of your data (original plus at least 2 different backups) + 2 backup locations (such as one backup on an external USB drive and another backup on a NAS) + 1 of those 2 backups should be stored offsite (in case of theft, damage, catastrophic failure).  Not everyone follows this, but the more diverse your backup are, the more chance of recovery you have if case things go bad. 

Unfortunately, recovering a deleted file does not guarntee it's integrity in every instance either.  Large files are stored in various sectors around the disk.  Any changes to the disk (any at all) can overwrite portions of that file as Windows will use whatever "free" space it feels is the best.  Recovery software tries to use algorithms to fill in missing sections of overwritten deleted data and sometimes is successful and sometimes not.  Free recovery tools like Recuva are usually OK if you immediately attempt a recovery before anything else is done, but with paging files and hibernation files in use and background updates, tasks like defrag or Microsfot indexing, etc, it's likely that data is already being overwritten to some exent for the deleted file.  That's why data recovery is such an expensive process when you send it to professionals.  If your data is critical and you're willing to spend money, I can highly suggest DriveSavers.  It ain't cheap, but they're good and they only charge if the data can be recovered and they give you the choice if you want to go through with it or not.