TI 2016 error in the service logs
Each time TI 2016 runs my nightly backup and validation and I review the logs there is an error reported. I can't tell from the logs what the error is and the logs report the backup and validation ran sucessfully. The error appears in logs from build 6559 and 6027. I'm attaching the logs. The log from April 8 is form build 6027 the one dated April 21 is from build 6559. The backup task seems to be working properly. I do a full backup with validation each night and retain 2 copies of the backup.
Any thoughts on the error in the logs?
I have noticed that I am unable to adjust the window size with B6559. The double ended arrows appear but clicking and dragging has no effect.
Build 6559 seems to have soem performance improvements. The task under 6559 takes about 2 hours to complete compared to the 5 hours shown in the B6027 log.
Attachment | Size |
---|---|
service_2016-04-08-02-00-09.log | 6.42 KB |
service_2016-04-21-02-00-06.log | 6.99 KB |


- Log in to post comments

I agree it appears to be a consolidation error, but the consolidation works correctly. I retain 2 copies, the current nights backup and the previous nights'. Both are there as expected. I will do as you suggested.
- Log in to post comments

It appears to me that the consolidation takes 2 tries to succeed. In the first log, event ID 13 generates the following message:
message=Consolidate Backup Archive Location: G:\Mynewbackups\Win_7_(C)_full_b20_s1_v1.tib Destination: G:\Mynewbackups\Win_7_(C)_full_b20_s1_v1_4F58E031-6847-44FE-BD56-431FAE9FC953.tib
Followed by the error message.
ID 14 generates the same message:
message=Consolidate Backup Archive Location: G:\Mynewbackups\Win_7_(C)_full_b20_s1_v1.tib Destination: G:\Mynewbackups\Win_7_(C)_full_b20_s1_v1_4F58E031-6847-44FE-BD56-431FAE9FC953.tib
But no error message.
I believe "Consolidation" is bad terminology and refers to the deletion of the old tib files IAW the task.
- Log in to post comments

I think your right Randy after looking at it again. Still probably no harm in getting it to the support team I suspect.
- Log in to post comments

Bob,
I agree that this should be sent to the support team.
Tom,
I recommend downloading and using the Log Viewer which can be found at:
https://forum.acronis.com/forum/115626
Regards,
FtrPilot
- Log in to post comments

I'm already using your log viewer FtrPilot , its a great help. I did submit my comments and the logs to the support team. The errors explain why it sometimes takes very long to complete the task. Up to 5 hours with B6027 about 2 hours with B6559. I have also been testing Macrium Reflect Free and it handles the exact same task in 1 hour and 10 minmutes or so with no errors. I can aslo read the logs directly from the application in plain text or XML.
- Log in to post comments

Tom, there is no problem with the backup in your case. What you see in between <error> and </error> is just a base64-encoded copy of the previous event, with a little more details that are useful only for Acronis developers.
Although it is technically possible to see logs, it is supposed that in 2016 version user checks that status of the backup by looking at status icon in GUI: whether it is green V-like or red cross, and not by reading through logs that might contain debug messages.
Thanks,
Slava
- Log in to post comments

Slava, yes there is no problem with the backups as they all validate.
Quite frankly the implementaion of the 2016 GuI is poor to say the least. I upgraded from 2014 where I could look at a summary that showed day by day exactly what happend and whether the backup was sucessful. Using the GUI to determine the status does work but it is not intuitive at all. I now have an email sent each night to confirm what is happening. This way I don't have to open the program unless the email indicates a problem.
- Log in to post comments