Aller au contenu principal

Consolidation into a single tib file -> Reliability?

Thread needs solution

Hello,

I've been testing the demo version of True Image 2013. I used to use a synchronisation tool to back-up my files to an external USB disk. Sadly I endured file corruption and it synced the corrupted files to my USB disk. I started looking for a back-up utility that can also store previous versions of files. TI2013 seems to do just that.

The interface looks great and user friendly. The settings are good and clear. But I noticed the back-ups are made into a single (or multiple) .tib file. This means that my 500.000 files are consolidated into one big archived file (with incremented files).

This introduces a risk. What if the archived file goes corrupt? I've been reading posts where people are reporting that the .tib file is corrupt and they loast *all* their files. If I make a back-up not using consolidated files I don't care if 1 of my 500.000 files is corrupt. But if the one file which holds all my 500.000 files is corrupt I .. have a problem.

How reliable is backing up to 1 tib file? Is it possible to back-up files 1:1, meaning there will be 500.000 files on the source ánd destination disk?

Thanks,
Bryan

0 Users found this helpful

If you wish to image an entire disk (my recommendation for safest option) or partition, the result is always a .tib archive. The only file-based options involve sync and Non Stop Backup, which don't image the entire system.

As I've explained in many posts, "Corrupted" is, unfortunately, a rather non-specific error message, in spite of its rather specific sounding term. It really just means that ATI can't validate the archive, which can be caused by disk errors or connection errors, rather than any problems with the .tib file itself. In many of those cases, the issue was caused by disk errors or poor connection of the external drive to the PC, not to any problems specifically with the .tib archive.

In my ten years using True Image on many PCs, I've had only two cases of the "corruption" error. In one case it was caused by the user's backup drive developing bad drive sectors, in the other case it was unclear but seemed to be caused by user copying the archive to a possibly failing drive and then copying that copy to another drive.

I've done entire disk restores hundreds of times, on many different PCs with differing hardware and OS. I've rescued friends and family after they've suffered complete hard drive failures, and they think I'm a hero when I install a fresh drive, restore from a True Image backup, and their system is back identical to what it was before the crash with no data loss.

I'm so confident in True Image, that I often use it to restore my system after testing software. I make a full disk backup. I install some software package I want to try. After working with the new app, if I decide not to keep it or if it causes problems to my system, I restore the backup and everything is returned to the state prior to when the new app was installed.

So, yes in principle a .tib archive is a single point of failure, but that's how all drive imaging tools work. Some ways to mitigate that risk: store multiple .tib archives from various dates; don't store them all on a single disk; supplement your images with file-based backup of your user data files.