Skip to main content

Can't open data stream to verify

Thread needs solution

I just upgraded to True Image Home 2011, and so far it's proven to be a major mistake. It doesn't give the feature I wanted (at least not without spending even more!), and the new UI is giving me fits, and the help isn't any better, discussing how to use a feature but not explaining how to find that window or dialog in the first place, which is my constant problem!

My existing scheduled backups are broken, since it didn't preserve the login credentials across the upgrade. Spent an hour trying to find where to enter them again! The new UI is pure madness! What's wrong with having a menu or something also? Arranging things for convenience only works for those use cases you've thought of, and re-entering credentials for an existing job is not one of them.

Anyway, I got the backup to run, and it created the file, but it gives an error on the validation step, "Failed to open data stream."
What's wrong? Is there another set of credentials somewhere hidden under a camouflaged rock?

Please help.

0 Users found this helpful

Hello John,

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

The error message "Failed to open data stream" is most likely caused by automatic cleanup rules. I would really appreciate if you could check this article, disable clean up rules and try running the backup one more time.

Thank you for your feedback regarding the program interface. I forwarded it to our Program management team and you can always submit your feedback from this link.

Please let me know if you have any other questions.

Thank you.

The file still existed, and I was able to view it and explore into it using a file explorer window.

Right now, it's telling me "not backed up yet" and "backup has successfully completed" at the same time.
The "Explore and recover" button is not present.

Going to the directory that is the subject of the backup, your Tab on the properties shows a backup from March 22 and March 26 (but not 27 or 28, and 28 is what "today at 7:00 AM" refers to in the main screen as being successfully completed.

Going to the directory that the backup places its file, I see files named for 24th through 28th inclusive, with 26 "touched" ten seconds after 28 was written. Files named for 22 and 23 are present using a different naming convention, from before I upgraded. They are touched along with 24 and 25 to indicate that they were all modified after writing the file for the 26th.

John,
My suggestion would be to create a new task and start a new chain in a new folder with a new name.

If you upgraded to a new build or version, while starting over is not required, to me, the safety and integrity of the backup will cause me to start a new chain.

In order for an incremental backup to be usable, all prior incremental backup must be present and readable and not corrupt. For example, if incremental backup #10 happens to have a problem, all more recent incremental backups are useless--which are a part of the backup chain.