All backups are failing on True Image 2019
In the last couple of days, all my backups are failing with a very unhelpful message which says nothing really except 'Error occurred'. In addition, clicking on 'More Information' just goes to a web page that says something like 'no further information on this error'.
I have 2 daily backups, one to an internal drive, and one to my NAS. Everything was OK till the last couple of days.
Where can I see a log file or something to get further info on this issue?
Attachment | Size |
---|---|
ti.jpg | 27.43 KB |


- Log in to post comments

Thanks Steve,
All I see is this kind of thing, does that mean anything to you:
22/11/2018 03:00:00: 00 13964 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
22/11/2018 03:00:00: 00 13964 I00640002: Operation Win10 Scan Backup started by schedule.
22/11/2018 03:00:02: 00 13964 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
22/11/2018 03:00:02: 00 13964 I013C0000: Operation: Backup
22/11/2018 03:00:02: 00 13964 I0064000B: Priority changed to Low.
22/11/2018 03:00:10: 00 13964 I000B03F0: Create Backup Archive From: C:\
D:\Iain User Folders\
To file: Win10 Scan Backup_inc_b1_s7_v1.tib Compression: Normal Exclude: System files
22/11/2018 03:02:31: 00 5884 I00640000: Writing incremental version to file: Win10 Scan Backup_inc_b1_s7_v1.tib
22/11/2018 03:05:49: 00 13964 E00040019: Error 0x40019: Error occurred while backing up.
22/11/2018 03:05:53: 00 13964 E013C0005: Error 0x13c0005: Operation has completed with errors.
Start: 22/11/2018 03:00:00
Stop: 22/11/2018 03:05:53
Total Time: 00:05:53
- Log in to post comments

You're right about the error message not being helpful, and the log doesn't add much. Is there anything in the Windows Event log showing a system or application error during the backup?
Steve, isn't there usually some module trace-back info logged for an error like this? Is its absence meaningful?
- Log in to post comments

Guys,
All backups, whether scheduled or manual, just fail as above. Both of my backups - to internal drive and NAS - fail at roughly the same place every time, i.e. a similar amount backed up.
I have looked at Windows Event Viewer, and can see no errors at the time of the backup failures in Application or System windows.
Any further ideas?
- Log in to post comments

Iain, in the MVP Log Viewer tool, switch the view from 'Short' to 'Regular' which will expose the more detailed internal log information for the error which may throw more light here.
- Log in to post comments

Thanks Steve,
The Regular log shows:
23/11/2018 16:20:10: +00:00 5696 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
23/11/2018 16:20:10: +00:00 5696 I00640002: Operation Win10 Scan Backup started by schedule.
23/11/2018 16:20:12: +00:00 5696 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
23/11/2018 16:20:12: +00:00 5696 I013C0000: Operation: Backup
23/11/2018 16:20:12: +00:00 5696 I0064000B: Priority changed to Low.
23/11/2018 16:20:19: +00:00 5696 I000B03F0: Create Backup Archive From: C:\
D:\Iain User Folders\
To file: Win10 Scan Backup_inc_b1_s7_v1.tib Compression: Normal Exclude: System files
23/11/2018 16:21:52: +00:00 10136 I00640000: Writing incremental version to file: Win10 Scan Backup_inc_b1_s7_v1.tib
23/11/2018 16:25:08: +00:00 5696 E00040019: Error 0x40019: Error occurred while backing up.
| trace level: error
| line: 0xce542e14da203c0d
| file: c:\bs_hudson\workspace\589\archive\backuper.cpp:1006
| function: Archive::BackupOperation::Execute
| line: 0xce542e14da203c0d, c:\bs_hudson\workspace\589\archive\backuper.cpp:1006, Archive::BackupOperation::Execute
| $module: ti_demon_vs_14110
|
| error 0x40003
| line: 0xce542e14da203bc3
| file: c:\bs_hudson\workspace\589\archive\backuper.cpp:932
| function: Archive::BackupOperation::ProcessItems
| line: 0xce542e14da203bc3, c:\bs_hudson\workspace\589\archive\backuper.cpp:932, Archive::BackupOperation::ProcessItems
| $module: ti_demon_vs_14110
|
| error 0x40003
| line: 0xce542e14da2039bc
| file: c:\bs_hudson\workspace\589\archive\backuper.cpp:413
| function: `anonymous-namespace'::BackuperHelper::ProcessTraverser
| line: 0xce542e14da2039bc, c:\bs_hudson\workspace\589\archive\backuper.cpp:413, `anonymous-namespace'::BackuperHelper::ProcessTraverser
| Path: D:/Iain User Folders/Music/iTunes/sentinel
| $module: ti_demon_vs_14110
|
| error 0x40002: The end of the file has been reached.
| line: 0xd18a9c757ef132f0
| file: c:\bs_hudson\workspace\589\core\include\file\file.h:27
| function: i_file::Read
| line: 0xd18a9c757ef132f0, c:\bs_hudson\workspace\589\core\include\file\file.h:27, i_file::Read
| $module: ti_demon_vs_14110
23/11/2018 16:25:12: +00:00 5696 E013C0005: Error 0x13c0005: Operation has completed with errors.
| trace level: error
| line: 0x9f2c53c72e8bcf27
| file: c:\bs_hudson\workspace\589\products\imager\demon\main.cpp:817
| function: main
| line: 0x9f2c53c72e8bcf27, c:\bs_hudson\workspace\589\products\imager\demon\main.cpp:817, main
| $module: ti_demon_vs_14110
Start: 23/11/2018 16:20:10
Stop: 23/11/2018 16:25:12
Total Time: 00:05:02
However, I have deleted the previous backups and restarted both. They ran OK without any errors. Still, I can't have any confidence that this will not happen again. Any further clues from the above?
- Log in to post comments

Iain, the detailed error log shows an issue with: Path: D:/Iain User Folders/Music/iTunes/sentinel plus the other point shown is that you are on build 14110. Acronis released build 14610 a couple of days ago but it is taking a little time to filter through the normal update system. You can download the new build via your Acronis account - also see the sticky post in this forum for this new update.
- Log in to post comments

Thanks Steve, I will update to the latest build. Any idea why new backups did not have any issue when run? What could the problem have been then with that sentinel file?
- Log in to post comments

Iain, sorry but no real idea as to why the old task had a problem with the sentinel file, it could have been locked, being updated etc, but if your task is using the default MS VSS snapshot service, that shouldn't have stopped the backup from working. The only time I have hit issues like this, it was my Antivirus flagging false positives for a suspect email virus, and that was a file in the snapshot volume, not the original of the same file on the disk! I didn't see anything in the log to suggest you have the same issue?
- Log in to post comments