Direkt zum Inhalt

Failed to open data stream backup error

Thread needs solution

I set up Acronis backup (latest Acronis True Image Home 2011 from my Windows 7 64 bit machine to NAS drive. I scheduled an incremental backup for each night with a full backup after 7 incremental ones. Everything worked fine for a couple of months, but for last several days I'm receiving "Failed to open data stream" backup error at the very end. What is strange, a backup file is created, but then this error occurs.  What could it be?

Anhang Größe
acronis-err.png 33.43 KB
0 Users found this helpful

Hello Vladimir,

Thank you for posting. I will do my best to help you.

Failed to open data stream error happens for a yet unknown reasons. The backups location can be a hard drive, NAS or FTP.

The fastest way to resolve this issue would be to contact our Support team with the following reports:

1. AcronisInfo report.

2. Wireshark logs.

3. Process monitor logs.

4. A detailed description of your backup settings.

The logs will be rather large, I would recommend to zip them and I will also follow-up with a private message where I will provide you with an ftp link. You can upload the reports there.

If you have additional questions, please let me know.

Thank you.

My main PC with LSI hardware RAID had a disk fail. Sparing you the details, I ended up restoring the whole-disk partition to a newly-configured drive (hint: "logically" not the same as before hardware failure) from Acronis. The restoration was fine, but subsequent backups using the same Acronis TI backup task generated the "Failed to open data stream" at the end of the task. This problem was resolved by creating a new backup task. (In my case, I happened to change my naming convention so that the new task is independent of the old task .tib files.) Including "validation" as part of the task does not seem to impact the problem, as demonstrated by a separate newly-created task.

So for me, the resolution of just deleting the old task that generated the failure and creating a new version of it resolves this issue.