TI 2016 makes keeps on making backups
TI2016 most recent build. I've been trying to get backups working on one client's computer. I'm an IT consultant. I just cleared out all the old backups and ran a partition backup for all the partitions on a 500GB Intel SSD C drive. Running Windows 7 professional 64 bit on a Dell Latittude laptop. The backup drive is a new WD 2GB passport external drive. I started the backup and found it had made a 165GB backup and then three smaller backups and Acronis was going to continue making more backups.
On another backup (I deleted the settings before starting this one) I got the error message, "The last backup failed. It will be restarted. Failed to open data stream." I don't know if this reflects the same problem with backups continuing to be made.
Is this a bug in Acronis or does it have something to do with the disk or Windows folders?
Thanks,
Alan
Will do.
Thanks,
Alan
Steve,
I make partition backups, not backups of the whole computer. I seem to remember in the past when I said to backup my whole computer it tried to backup secondary drives and even external drives. If I make a whole computer backup will it just do the C drive and partitions on that drive?
Thanks,
Alan
The best way to get a C; drive backup is to select that drive only in the disk and partitions backup screen. At the bottom of that screen you will see an option to show all partitions, select that to insure that all partitions on disk C: that you want to include in the backup are selected.
That's what i thought.
Thanks,
Alan
Steve,
If I increase the error time to hours won't that increase the time for the backup to complete for hours?
The log shows the following error:
id=41; level=2; module=100; code=0; date/time=14/06/2016 07:25:56
message=The following backups have been successfully created: Z:\new full 1\Crucial_CT500MX200SSD1_inc_b3_s3_v1.tib
id=42; level=4; module=485; code=14; date/time=14/06/2016 07:25:56
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=AQ4A5QE4RaELzE1bbUZhaWxlZCB0byBvcGVuIGRhdGEgc3RyZWFtLiBUcnkgdG8gcmVtb3ZlIHRoZSBiYWNrdXAgZnJvbSB0aGUgbGlzdCwgYWRkIGl0IGFnYWluIGJ5IGNsaWNraW5nICdCcm93c2UgZm9yIGJhY2t1cCcgYW5kIHJlY3JlYXRlIHRoZSBiYWNrdXAgc2V0dGluZ3MuACRtb2R1bGUAQXRpX2RlbW9uX3ZzXzY1NzEAJGZpbGUAQWs6XDY1NzFccHJvZHVjdHNcaW1hZ2VyXGFyY2hpdmVcaW1wbFxvcGVyYXRpb25zXGFyY2hpdmVfb3BlcmF0aW9uX2Nsb25lLmNwcAAkZnVuYwBBVHJ1ZUltYWdlOjpBcmNoaXZlOjpDbG9uZUFyY2hpdmVPcGVyYXRpb25JbXBsOjpQcmVwYXJlACRsaW5lAE46BwAAAAAAAADpAwsAOEWhC8xNW21GYWlsZWQgdG8gb3BlbiBkYXRhIHN0cmVhbS4gVHJ5IHRvIHJlbW92ZSB0aGUgYmFja3VwIGZyb20gdGhlIGxpc3QsIGFkZCBpdCBhZ2FpbiBieSBjbGlja2luZyAnQnJvd3NlIGZvciBiYWNrdXAnIGFuZCByZWNyZWF0ZSB0aGUgYmFja3VwIHNldHRpbmdzLgAkbW9kdWxlAEF0aV9kZW1vbl92c182NTcxACRmaWxlAEFrOlw2NTcxXHByb2R1Y3RzXGltYWdlclxhcmNoaXZlXGltcGxcb3BlcmF0aW9uc1xhcmNoaXZlX29wZXJhdGlvbl9jbG9uZS5jcHAAJGZ1bmMAQVRydWVJbWFnZTo6QXJjaGl2ZTo6Q2xvbmVBcmNoaXZlT3BlcmF0aW9uSW1wbDo6UHJlcGFyZQAkbGluZQBOOgcAAAAAAAAADQDlAZtEoQvMTVttACRtb2R1bGUAQXRpX2RlbW9uX3ZzXzY1NzEAJGZpbGUAQWs6XDY1NzFccHJvZHVjdHNcaW1hZ2VyXGFyY2hpdmVcaW1wbFxvcGVyYXRpb25zXGFyY2hpdmVfb3BlcmF0aW9uX2Nsb25lLmNwcAAkZnVuYwBBVHJ1ZUltYWdlOjpBcmNoaXZlOjpDbG9uZUFyY2hpdmVPcGVyYXRpb25JbXBsOjpJbnNlcnRBcmNoaXZlSW5mbwAkbGluZQBOnQYAAAAAAAAA
id=43; level=4; module=11; code=1001; date/time=14/06/2016 07:25:56
But this seems to happen after the backup has been successfully created. Any idea what that would occur?
Alan, increasing the delay time to hours should prevent the multiple new backups running every 10 minutes that you reported and may allow ATIH to end the task more gracefully and write more informative messages to the log file. This has worked for others who were getting similar repetitive error message notifications & backup segments.
Not sure why the log is showing the Failed to open data stream. message unless there is an issue with the new WD 2GB passport external drive going to sleep and not responding for some reason?
I'm not sure why I got into this business 34 years ago. I should have been a farmer. But it's too late now.
OK, so backups work to the customer's 500GB Seagate external drive.
They work to the WD passport when I choose to put them straight on the Z drive. (As the destination in Acronis.)
When I create a backup folder and browse to that folder on the Z drive as the backup destination, they do not work, no matter how small a file I backup and no matter how long the error recovery time. It backs up the file but I get an error message.
WD problem? Acronis problem? Have I offended a local god?
Customer is in California. I'm in New York and can only work on her computer til 11:30EST.
I'll proceed tomorrow.
Make sure that the backup schedule settings are matching your requirements. It is possible that the internal ATI task scheduler has some remnant of data if the behavior is not what the settings say it should be. You can use the acronis schedule manager to clean up the schedules of the tasks.
The failed to open data stream error can typically be fixed by creating a new task, preferably in an empty directory. Causes can include the corruption of the internal database of Acronis true image. You can shut down the program, delete the database folder in c:\programdata\Acronis\TrueImageHome. If Acronis complains that the file is open, you might have to stop the Acronis services using services.msc.
Another way of fixing the issues is to uninstal ATI, reboot and reinstall, then create new tasks in empty directories.
I renamed the database folder per what Pat L said and I think that did it. Must have been a corruption of that folder.
Thanks to everyone who helped. I learned a lot about how Acronis works.
Alan
Steve,
I've been thinking of taking the number of error retries down to 2 or 3 and setting the delay time to 2 hours as a standard practice whenever I set up backups. Is this a good idea?
Thanks,
Alan
Alan, from what I have seen, the number of error retries setting is ignored by ATIH if the cause of the error is still present - this was still so for the ATIH 2017 Beta I have been testing.
Setting the delay time to 2 hours will help minimise the impact of any error retries if they are still occurring.