Serious issue when opening encrypted tib
Hi,
I am using Acronis True Image Echo Server with Universal Restore at work for backup of my harddisk.
(At Home I am using Acronis True Image Home Version 2009)
Over the years I have created a good amount of backups most of them are full backups but some are incremental or differential backups. I created about 2-3 backups per year. All of these backups are password protected. i noted down the password on a piece of paper.
A few years back I have tried to restore without any problem. The backups are stored on a external harddisk.
Recently the worst case happened. The harddisk stopped functioning and I urgently needed a file. In my hurry a booted the home version i.e 2009 instead of the version used for backup and tried to restore the last version, but I got an error message that the supplied password is not correct. So I tried with the next previous version but soame result and the one more previous version but again same error.
Only then I realized, that I have booted the wrong version. Therfor I changed CD and booted True Image Echo Server with Universal Restore (same CD used for backup) and tried to restore but I got exactly same error message! (Let me not talk of the raising panic)
So now I went back to systematically try to open the stored backups from newer to older version and I was successful at some point 3 years back. This version let me called it lastworking is full backup and the next following a differential backup.
I was able to open the fullbackup with the noted password but not the newer differential backup ! but i know to create the differential backup you have to supply the correct password during craetion. Threfor I am sure the noted password is correct. But why does the tool always tell me the supplied password is incorrect?
Now here are my questions:
1. Is it possible that opening encrypted Acronis True Image Echo Server with Universal Restore backup files with the Home version can corrupt these files ?
2. How is it possible to check if an encrypted tib file is not corrupted. Maybe not fully or at least the file header?
Thanks and best regards

- Log in to post comments