Skip to main content

The file is corrupted

Thread needs solution

That's the less than useful message I now get from 2 x ATI2020 installations which have successfully been doing sheduled weekly custom full image backups.  So I've had to create new repositories and start again.  But the old repositories are needed, how do I recover them?

One possible commonality - on both systems I recently houskeeped the number of saved images and reduced the total by half or more.  But I did that using the "Clean up versions action".

Once again this prooves how stupid Acronis 'tibx' format is, if backups cannot be truly standalone.

Any recovery ideas anyone?  (image attached)         

 

 

 

image 308

0 Users found this helpful

David,

In all likelihood, it is the database which has issue and not the backups themselves.  My suggestion is to Remove the backup task for these backup files from the application GUI then, add the backup files back into the application GUI, reconfigure the task (only a minimal amount of configuration required), and then run the task to get things back on track.

To remove the task and retain the remaining backup files, click on the carat (v) to the right of the task name in the backup list and from the menu that appears select Delete.

Next click on Remove to remove the task from the backup list in the GUI.  Backup files will remain undisturbed.  Once that task is removed you will need to add it back in the list.  To do that look to the bottom of the task list column to where the Add backup appears.  To the right of that is another carat (v), click it and select Add existing backup.  This will open an explorer style window, navigate to the backup file location where the task in question here stored its backup files.  Once the backup files are showing click to select the first file in the list and click on the Add button.   This will import the task back into the GUI. 

You will see that the task will display a button now that says Reconfigure rather than Back up now.  Click on the Reconfigure button and you will be prompted to either re-select the backup files location or, you may be prompted to re-selected the source data.  In either case do as instructed and once you have completed this step the GUI will now display the backup task with a Back up now button appearing.  Click on the Back up now button to run and save the task again.

This should correct the behavior you write about.

Thanks.  I gave those steps a go on one of my machines.

Got as far as the Add button to add my first backup back in and this pops up:

failed to add 0

Well I ignored it and went on and did "reconfigure" and got this  ..

failed to open

I think I'm stuffed.

Let this be a awarning to everyone.  The current Acronis 'system' which relies on multiple files being uncorrupted in order to just recover one of them is deeply flawed for a system which is supposed to provide BACKUPs.

Avoid !

 

 

Clutching at straws here. You could try copying the backup files to a local dive as there is a possibility that the problem is network related. Over the years there have been reports of problems when recovering from a NAS, and copying the backup files to a local drive (including USB drive attached to the computer) has allowed the recovery.

Ian