"Failed to open data stream" error
I've been using Acronis True Image 2015 for almost two years now. About a week ago, I started getting "Failed to open data stream. Try to remove the backup from the list, add it again by clicking 'Browse for backup' and recreate the backup settings." I've done that, and the next backup runs as a full backup, apparently successfully (I see a good file in the backup directory). However, at the end it immediately spits out the above message, then starts up incremental backups one after another, until I stop them. The next day, at the regularly scheduled time, the incrementals start running amok again.
How do I recover from this?
TIA for your help.
Thanks Steve!
I installed the viewer and am looking at the log. Briefly, I see:
id=50; date/time=10/4/2016 4:42:04 PM; message=The following backups have been successfully created: E:\Acronis Backups\MyBackups_inc_b1_s43_v1.tib
id=51; date/time=10/4/2016 4:42:08 PM; message=Failed to open data stream. Try to remove the backup from the list, add it again by clicking 'Browse for backup' and recreate the backup settings.
Error_Code=AQ4A5QEwRaELzE1bbUZhaWxlZCB0byBvcGVuIGRhdGEgc3RyZWFtLiBUcnkgdG8gcmVtb3ZlIHRoZSBiYWNrdXAgZnJvbSB0aGUgbGlzdCwgYWRkIGl0IGFnYWluIGJ5IGNsaWNraW5nICdCcm93c2UgZm9yIGJhY2t1cCcgYW5kIHJlY3JlYXRlIHRoZSBiYWNrdXAgc2V0dGluZ3MuACRtb2R1bGUAV0M6XFByb2dyYW0gRmlsZXMgKHg4NilcQ29tbW9uIEZpbGVzXEFjcm9uaXNcVHJ1ZUltYWdlSG9tZVxUcnVlSW1hZ2VIb21lU2VydmljZS5leGUAAOkDCwAwRaELzE1bbUZhaWxlZCB0byBvcGVuIGRhdGEgc3RyZWFtLiBUcnkgdG8gcmVtb3ZlIHRoZSBiYWNrdXAgZnJvbSB0aGUgbGlzdCwgYWRkIGl0IGFnYWluIGJ5IGNsaWNraW5nICdCcm93c2UgZm9yIGJhY2t1cCcgYW5kIHJlY3JlYXRlIHRoZSBiYWNrdXAgc2V0dGluZ3MuAAANAOUBk0ShC8xNW20AAA==
id=52; date/time=10/4/2016 4:42:08 PM; message=Failed to open data stream. Try to remove the backup from the list, add it again by clicking 'Browse for backup' and recreate the backup settings.; line_tag=0x6D5B4DCC0BA14530; hide=1
id=53; date/time=10/4/2016 4:42:08 PM; message= ; line_tag=0x6D5B4DCC0BA14493; hide=1
id=54; date/time=10/4/2016 4:42:08 PM; message=ServerLRPC::_CloseConnection id=11,848
id=55; date/time=10/4/2016 4:42:08 PM; message=ServerLRPC::_CloseConnection id=15,052
id=56; date/time=10/4/2016 4:42:08 PM; message=ServerLRPC::_CloseConnection id=8,480
id=57; date/time=10/4/2016 4:42:08 PM; message=ServerLRPC::_CloseConnection id=11,848
id=58; date/time=10/4/2016 4:42:08 PM; message=ServerLRPC::_CloseConnection id=15,052
id=59; date/time=10/4/2016 4:42:08 PM; message=ServerLRPC::_CloseConnection id=8,480
id=60; date/time=10/4/2016 4:42:10 PM; message=Operation has completed with errors.; line_tag=0x9F2C53C72E8BCE18
Error_Code=AQUAPAEYzosux1Msn09wZXJhdGlvbiBoYXMgY29tcGxldGVkIHdpdGggZXJyb3JzLgAkbW9kdWxlAFdDOlxQcm9ncmFtIEZpbGVzICh4ODYpXENvbW1vbiBGaWxlc1xBY3JvbmlzXFRydWVJbWFnZUhvbWVcVHJ1ZUltYWdlSG9tZVNlcnZpY2UuZXhlAAA=
Start= 10/4/2016 4:00:02 PM
Finish= 10/4/2016 4:42:10 PM
Obviously don't understand the errors codes. The full log is attached.
I did see I/O errors as the backup ran. I scanned all drives, which came up clean.
The output drive is E:, which is unchanged. I can see the backup files in the E:\Acronis Backups directory.
Thanks again!
Mark
Mark, thanks for the full log file, this shows some earlier errors before you see the data stream error message:
id=42; level=2; module=11; code=1008; date/time=04/10/2016 22:01:34
message=Create Backup Archive From: C:\Users\Mark\Desktop\ C:\Users\Mark\Documents\ C:\Users\Mark\Downloads\ C:\Users\Mark\Music\ C:\Users\Mark\Pictures\ C:\Users\Mark\Videos\ F:\ To file: MyBackups_inc_b1_s43_v1.tib Compression: Normal Exclude: System files
id=43; level=2; module=100; code=0; date/time=04/10/2016 22:04:48
message=Writing incremental version to file: MyBackups_inc_b1_s43_v1.tib
id=44; level=2; module=4; code=1; date/time=04/10/2016 22:24:28
message=Error occurred while reading the file.;
id=45; level=2; module=4; code=1; date/time=04/10/2016 22:24:28
message=Error occurred while reading the file.;
id=46; level=2; module=0; code=65520; date/time=04/10/2016 22:24:28
message=The request failed due to a fatal device hardware error;
id=47; level=2; module=4; code=1; date/time=04/10/2016 22:33:08
message=Error occurred while reading the file.;
id=48; level=2; module=4; code=1; date/time=04/10/2016 22:33:08
message=Error occurred while reading the file.;
id=49; level=2; module=0; code=65520; date/time=04/10/2016 22:33:08
message=The request failed due to a fatal device hardware error;
id=50; level=2; module=100; code=0; date/time=04/10/2016 22:42:04
message=The following backups have been successfully created: E:\Acronis Backups\MyBackups_inc_b1_s43_v1.tib
id=51; level=4; module=485; code=14; date/time=04/10/2016 22:42:08
message=Failed to open data stream. Try to remove the backup from the list, add it again by clicking 'Browse for backup' and recreate the backup settings.
The above errors suggest a problem with files in the source data when this is being read, but could indicate something more serious given the subsequent: 'fatal device hardware error' message.
Acronis states that the backup has been successfully created, so I would suggest trying to mount the backup archive and then do a comparison between the source data and the backup archive contents to see if this indicates that any files are missing or sizes are different etc.
Beyond that, running a full CHKDSK /F /R against your C: & F: source data drives to check for any bad sectors on these drives would be recommended.
I'd also be looking at other tools to see if the hard drive is physically failing since a fatal device hardware error is being reported. Grab the free version of hard disk sentinel and see what it reports on the health and estimated remaining life expectancy of your source drive. If it says there is an immenent failure, you better look to replace your drive ASAP.
OK, I've ran CHKDSK against C:, F:, and E: (the backup disk). No errors found on the last two. No way to tell AFAIK on C:. I installed Hard Disk Sentinel, which tells me all my disks are PERFECT, and that my C: drive should be good for another 1000 days. In any case, I ran an incremental backup after that, with the same result as before.
Not sure where I go from here.
If you create a new backup task with a unique name and reselect the source and destination, does it still error out the same way? If so, I'm not sure either.
My only other thought is that you may have either some database corruption that occured somewhere or that you have a bad incremental somewhere in the chain.
How many incrementals are there - 43? Did you move any or delete any manually at some point? How much time has there been between the original full and the latest working backup of the incremental? How often does your backup run - daily, weekly, etc?
If you can create a new backup task and it works, then chances are it's the backup task or something has gone wrong with your incrementals along the way. Incrementals are good for speed and saving space, but also more volatile than fulls or differentials because they are depenedent on every single file in the chain that came before it. IF something goes wrong with #10, then 11-every other one that came after #10 are toast, even if validation says they're OK.
Let's assume you are on version 43 and are taking daily incrementals (44 days of backups) - that's a long time to go without a full when daily backups are being done. In an enterprise enviorment, if doing daily backups, you'd typcially do 1 full, followed by 6 incrementals so that there is a full each week... this limits chance of corruption/failure of incrementals over time and also gives you restore points with a full at more frequent intervals. Better to only lose a weeks worth of data (if you can afford to), then say a month, or longer.
If you're doing weekly backups with an incremental each week, then you're banking on close to a years worth of data and only a single full, which is also risky because of the length of time involved that has occured since the original full.
Try creating a new backup task and see if that works. If it does, then it might be time to consider a different backup scheme and not letting the incrementals build up for too long or too many.
There are 43 incrementals because when it gets into this state, it runs incrementals one after another, continuously, until I stop them. I have ran full backups, which complete successfully, then this error pops up and incrementals start running amok. I have defined entirely new backups, with the same result.
My E: (backup) drive is 5.5 TB, but a full backup is >800 GB (lots of high-res photos), so there isn't room for very many full backups. I set up for 60 incrementals between full backups, understanding the risks (purging after 6 months). This has worked well for over a year now. That is, until a week or so ago.
OK, I've ran CHKDSK against C:, F:, and E: (the backup disk).
Did you run it with the /F /R switches as suggested above- without those, it may not move or repair anything either. There have been a few forum posts where users only ran the default CHKDSK without the switches and no change, but after running if /F /R then backups would run again.
Beyond that, last 4 suggestions I can suggest. None are guaranteed to work if there truly is a disk issue or connectivity issue, but if it's related to Acronis somehow, then #4 should do it.
1) Run the taskscheduler and use the taskzap command to blow away all scheduled tasks (including possible "ghost scripts" that may be lurking in the shadows. Delete your current backup job in Acronis and start with a new one using a completely unique backup name and see how it goes from there.
2) Re-run the original installer (download from your account to make sure you have the latest available) and be sure to right click and "run as administrator" even if logged in with admin. You should get the option to "repair" and that might do the trick.
3) Some users have had database corruption ast some point in time. Instead of having to do #4, they simply delete the database (not the backups) and let it rebuild itself. https://forum.acronis.com/forum/101541#comment-367973
4) If all else fails, many users have had luck doing a completely fresh install after using the cleanup tool (use these instructions as they are more thorough than others posted elsewhere) - especially if they've upgraded from older versions of Acronis, and/or had Acronis installed as part of an OS upgrade.
Personally, I'd go for the clean tool and just get it overwith. If you follow #4 and that doesn't fix a problem with Acronis, time to start searching your Windows system and application logs for signs of trouble with your hardware and/or OS.
I uninstalled and reinstalled, and defined a new backup. I've successfully run a full and an incremental backup, so think I'm good.
Thanks for all the help. Much appreciated!
Good deal. We may never know the original issue, but sometimes just starting fresh is the best route anyway. Hopefully all is well from here on out.