Failed to open backup It may be inconsistent or corrupted

Dvir,

The problem is that TIH cannot see the original full image that it made. Have you renamed or moved the first full image which should be named My patitions_full_b3_s1_v1.tib. If you could provide a screen shot of what you see in Windows Explorer it would be of great help.

I notice that this is slice 32 and that some files have been consolidated, something doesn't seem right here.

Are you able to make a new task and see if that runs without errors?

Is 'F' an external drive or an internal one?

Hi Colin,

Thanks for your answer.
For 3 days ago I got success backup report, but now again I get the same problem.
As you say I tried to delete all backups and the task backup, after that try new task backup of incremental back but I getting the same problem.
The 'F' is an external drive.

Any other suggest?

Thanks,

I have the EXACT same issue that seems to have started about a week ago. I had the backup set to 'Version Chain' and it was working fine for weeks then it kept complaining I was out of space even though I had it set to delete the oldest backup. I deleted all backups and changed the backup type to 'Incremental' and told it to delete the oldest every 7 days. Since I did this it gives me the "Failed to open backup It may be inconsistent or corrupted". I haven't been able to have it do a backup without this message appearing although it seems to have completed the backup. Will try to set it back to 'Version Chain' to see if it works again but it's driving me crazy.

@Nelson,

If you edited the original task to incremental, True Image may well fail. It is better to delete the task and make a new one.

I have this pattern. I am sure that after upgrading, moving files around, losing a hard drive, trying to move backups, trying to recover space from backups I don't need, and not understanding best practice, I have confused the catalog. Now, every backup that happens ends in a message about not being able to open tib files that I had hoped were no longer needed.

I removed the task from the list and created a new task, but the fault reoccurs.

I am now trying to delete the whole backup, as I have the really important files backed up on another channel while I try to resolve this. That seems to have been the wrong thing to do. I have been watching the spinning "Deleting Backup" for a half hour, now, and haven't seen any progress, and haven't seen any activity on any of the disks.

First of all I apologize for my bad english... Using my desktop computer (O.S. WINDOWS 7 home premium edition) the "on line back up server" is often inaccessible, while using the APP on my iPhone the on line back up works better. Do you know the reason? Thank you so much.

I have an uptodate version of Acronis 2014 on Windows 8, I back up to a USB hard disk. When I try to recover (file or disc) I get messages "Failed to open" or "Failed to recover. When I do "Open Location" or use Windows Explorer the file which it says it cannot access is clearly exists on the disc. The Log says the backup was successful. I've looked in the Knowlwdge Base but nothing there seems relevant. I could of course delete the files on the USB disc but Acronis would not know so that would creare more problems. Is there any way out of this? I have tried deleting all the disc versions (More features/Remove from list) and doing a new disc backup but it says that it cannot open a My Partitions folder on the USB disc to hold the backup - there is no such folder so I created one and tried to run the backup again. This time it worked and appeared to complete without any error messages. When I clicked "Recover" it displayed the page to recover partitions and there were no error messages. I didn't do a recovery but at least it had found the backup file. Howeve I now can't recover my File backups!!! This software is driving me mad. Has anyone any idea how it (doesn't) work and hoe it can be fixed?

Validate the backup. If ATI can't validate it, that can be caused by disk errors or connection errors, rather than any problems with the .tib file itself.

Validation failure is often due to hardware issues. To troubleshoot, see Grover's new backup and restore guides http://forum.acronis.com/forum/29618 and http://kb.acronis.com/content/1517

Run chkdsk /r on each partition of the internal drive, and on the external HD. If there are hidden partitions, assign letters to them so you can chkdsk.
Also run a drive checking utility from the drive manufacturer, as those sometimes catch errors missed by chkdsk.

Don't connect via a hub, a port in a monitor, a USB extension cord, etc. Connect the external drive directly to a USB port on the rear of the computer case.

As you're backing up to an external USB HD, you should assign a fixed drive letter to the external drive, high in the alphabet (e.g. V) to avoid its letter changing.