Aller au contenu principal

Backup fails with "Failed to open data stream"

Thread needs solution

Acronis 11 has been failing for about 2 months now. According to the logs, it is getting past the validation step and is failing to open a file during the Consolidate step:
message="Failed to open data stream."
message="The specified file does not exist."
K:\My backups\OS_(0)6.tib.

The latest backup is OS_(34)[null through 6].tib. I assume the (0) in the file name in the log is a parameter.

Being without a backup is making me nervous. Please help!

0 Users found this helpful

Penny,

Just create a new backup task, with a new name to another directory. When your older backups will be old enough, just delete the corresponding task(s) within ATI and delete the orphaned TIB files manually.

Thank you, thank you, thank you Pat - from the bottom of my heart. This worked! I can't tell you how grateful I am to find a solution to this dilemma.

One other minor issue - though we have the program set to automatically delete the oldest version(s) when the backup disk is full, Acronis has not yet done that. We've needed to do it manually when we get a "disk is full" message. Would you (or anyone) have any idea how to make that setting work?

Now that we've gotten our thorniest problem solved, I may very well go ahead and purchase the 2012 edition.

Thanks again, Pat!

The best setting with 2011 and 2012 is something like this:
- backup scheme: custom
- choose full, incremental or differential; I recommend incremental, but any is fine,
- set to do a new full backup after X incrementals. X depends on how often you do backups, how many changes your doing, etc. A rule of thumb is to keep it low enough so that the last full is never tool old for you to go back to, if you ever had to. I recommend to do a new full weekly (ie after 6 incrementals) for a daily backup, or a new full monthly (if after 4 incrementals) for a weekly backup, for example,
- turn auto cleaning on,
- set ATI to keep Y most recent chains (a chain is one full + X incrementals). Choose Y as big as possible knowing that you need enough space for Y+1 chains on your disk.

Whenever you want to change the backup name, destination, backup scheme or retention rules, it is better to create a new task in a new directory.

I have experienced this problem numerous times over several months, on two different computers using v2011. I see that users of v2012 also are having this problem with error messages about failure to open a data stream, whatever that means. I've searched the knowledge base for information from Acronis, but find only users sharing workarounds that -- at least in my case -- work only sometimes. Starting a new chain or revising the script provides no long-term solution.

The purportedly corrupt backup images actually seem to be OK despite the error messages, but I can't trust them. With so many failure messages, I have little left except questionable images. As a side note, none of the automatic cleanup scripts has ever worked for me. I am reluctant to upgrade to 2012 because of my bad experiences with v2011. Also, I'm offended that Acronis charges for support.

If any Acronis representative reads this, I would encourage the company to resolve this problem.

Frustratingly, I have had this same problem (as have many others on this forum it seems) for a year or two. I am backing up a Windows 7 PC to a Readynas Pro.

After a number of cycles of successful backups, Acronis decides to consolidate backups, then fails with "Failed to open data stream".

I can reset the problem by deleting and recreating the backup task, although it's a pain. However the problem then comes back a few weeks later. I upgraded to 2012 but no result. I filed a support request but got no answer; and now it seems my support has expired.

There are two problems:
(1) True Image doesn't seem to be able to execute a consolidation process on a NAS;
(2) I don't understand why it is consolidating at all. My backup scheme is differential, create full after every 5, store no more than 3 recent chains, do not delete first version. Surely that should cause it to delete old chains, not to consolidate them?

That is right, with these settings it should not consolidate. Are you sure you turned on auto-cleaning and not consolidatation? Do you ming posting a screenshot of your backup settings/options?

Screenshot is attached as requested, and also the backup log screen.

Fichier attaché Taille
97721-100675.jpg 64.38 Ko
97721-100678.jpg 151.14 Ko

Looking at your settings and your log, I am not sure what "consolidate" really means. It might be a bug in the way the log reflects the auto-cleaning process, or some more obscure step... At any rate, I would not worry about this word.

More concerning is the failed to open data stream... The basic step to resolve this type of issue is to create a new task and see if the problem subsist.

I think it is trying to consolidate.

Creating a new task (which I have now done several times with 2011 and 2012 versions) gets me moving again - but then after a couple of weeks (can't recall the exact time) it starts failing every night. Almost as though it had reached a trigger point and was starting to do nightly consolidations...?

Does this problem occur precisely when it is supposed to clean up?