Skip to main content

Is my backup hosed?

Thread needs solution

Hi all,

I created a backup of a full disk image called "SSD Pre-Wipe" and set it to Single Version Chain. 

Later, after a clean install of Windows, I did another backup of the same drive, but changed the backup name to "SSD Clean". I did not realize that renaming the backup job wouldn't keep the original TIB, but instead deleted the original AND renamed the new backup. I wish there was a warning or something.

I used R-Studio to restore the TIB that was deleted. I have no idea if the same bytes were overwritten or not, but when I to open or read the TIB now, it says it is corrupt. The old backup is over 200GB and the new is around 50GB, so there's certainly a possibility of about 150GB of completely restorable data if only the TIB was able to be opened despite being corrupt. Is there anything I can to do to read clunks or bits of the recovered TIB? I am assuming that with the Acronis compression and proprietary format, I may be out of luck.

Any ideas?

0 Users found this helpful

Nick, sorry but when you select a Single Version Chain, the software automatically deletes the previous version of the backup file immediately after a new file has been successfully created, this is regardless of changing the task name.

Unfortunately, if you have recovered the old backup .TIB file and this is now shown as being corrupt then there is a very strong possibility that it is unrecoverable.  The mechanism for checking the integrity of the file is to try to perform a validation for it.  You can do this by right-clicking on the file in Explorer and taking the Validation option from the True Image menu option shown.

Validation will compare the checksum embedded in the file when it was created with the value calculated now from the file as it is today.

Double-clicking on the .tib file will try to open it to let you browse its contents, but if this doesn't work and the validation fails, then it is likely that some parts of the file were unable to be recovered fully or were overwritten during normal system operations on the computer.