Skip to main content

Success messages lists error messages

Thread needs solution

ATI has always had a peculiar view of success. I was trying to include my local OneDrive directory in a backup, and I got all of this:

2018-09-24T02:00:00:318-04:00 17724 I00640002: Operation Critical Docs to Cloud started by schedule.
2018-09-24T02:00:24:240-04:00 17724 I013C0000: Operation: Backup
2018-09-24T02:00:24:250-04:00 17724 I013C0000: Backup type: file level
2018-09-24T02:00:24:292-04:00 17724 I013C0000: Operation: Consolidation
2018-09-24T02:00:24:293-04:00 17724 I0064000B: Priority changed to Low.
2018-09-24T02:03:28:030-04:00 24956 W00170810: Error 0x170810: Failed to enumerate directory 'C:/Users/Jerry Schwartz/OneDrive/'. It may be corrupted or does not exist. Please check the disk for errors.
| trace level: warning
| line: 0xa61565b622786e59
| file: c:\bs_hudson\workspace\544\archive\ver2\file\backup_operation.cpp:2349
| function: ArchiveApi::ItemWithSubitemBackuperImpl::CountProgressStatistic
| line: 0xa61565b622786e59, c:\bs_hudson\workspace\544\archive\ver2\file\backup_operation.cpp:2349, ArchiveApi::ItemWithSubitemBackuperImpl::CountProgressStatistic
| Path: C:/Users/Jerry Schwartz/OneDrive/
| $module: ti_demon_vs_13660
|
| error 0x4000c: The file is read-only.
| line: 0xf35f747b3b21fc69
| file: c:\bs_hudson\workspace\544\core\file\windows\winnt_dir.cpp:1376
| function: winnt_dir::iterator::iterator
| line: 0xf35f747b3b21fc69, c:\bs_hudson\workspace\544\core\file\windows\winnt_dir.cpp:1376, winnt_dir::iterator::iterator
| function: FindFirstFileW
| path: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy77\Users\Jerry Schwartz\OneDrive\*
| $module: ti_demon_vs_13660
|
| error 0xfff0: The media is write protected
| line: 0xbd28fdbd64edb8f1
| file: c:\bs_hudson\workspace\544\core\common\error.cpp:307
| function: Common::Error::AddWindowsError
| line: 0xbd28fdbd64edb8f1, c:\bs_hudson\workspace\544\core\common\error.cpp:307, Common::Error::AddWindowsError
| code: 0x80070013
| $module: ti_demon_vs_13660
2018-09-24T02:03:28:045-04:00 17724 W00170811: Error 0x170811: Failed to back up directory 'OneDrive'.
| trace level: warning
| line: 0xa61565b6227869dc
| file: c:\bs_hudson\workspace\544\archive\ver2\file\backup_operation.cpp:1200
| function: ArchiveApi::ItemBackuperImpl::BackupCommonAttributes
| line: 0xa61565b6227869dc, c:\bs_hudson\workspace\544\archive\ver2\file\backup_operation.cpp:1200, ArchiveApi::ItemBackuperImpl::BackupCommonAttributes
| TargetPath: C:/Users/Jerry Schwartz/
| ItemName: OneDrive
| $module: ti_demon_vs_13660
|
| error 0x4000c: The file is read-only.
| line: 0xf35f747b3b21fcdf
| file: c:\bs_hudson\workspace\544\core\file\windows\winnt_dir.cpp:1494
| function: winnt_dir::iterator::GetInodeInfo
| line: 0xf35f747b3b21fcdf, c:\bs_hudson\workspace\544\core\file\windows\winnt_dir.cpp:1494, winnt_dir::iterator::GetInodeInfo
| function: OpenFileW
| path: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy77\Users\Jerry Schwartz\OneDrive
| $module: ti_demon_vs_13660
|
| error 0xfff0: The media is write protected
| line: 0xbd28fdbd64edb8f1
| file: c:\bs_hudson\workspace\544\core\common\error.cpp:307
| function: Common::Error::AddWindowsError
| line: 0xbd28fdbd64edb8f1, c:\bs_hudson\workspace\544\core\common\error.cpp:307, Common::Error::AddWindowsError
| code: 0x80070013
| $module: ti_demon_vs_13660
2018-09-24T02:12:50:448-04:00 17724 I013C0006: Operation has succeeded.
 

That doesn't look like success to me.
 

0 Users found this helpful

Jerry, this is the OneDrive issue with reparse points for OneDrive FilesOnDemand that I just mentioned in my response to your other post in this forum.

Steve Smith wrote:

Jerry, this is the OneDrive issue with reparse points for OneDrive FilesOnDemand that I just mentioned in my response to your other post in this forum.

This is a different and longstanding issue. ATI, as far back as I remember, will report success even though the logs show problems. I inspect each report to make sure there's nothing out of the ordinary, but the program shouldn't require that.

In the case of the message above, the email said success even though the log is full of scary stuff and, as you pointed out, the OneDrive files were not successfully backed up.

The program, any program, should not report success unless it did everything the user wanted.

Part of the issue here Jerry is that Acronis have included a level of message detail that is really only understandable by their developers in these logs, where that detail should be left out unless the user is requested to enable it for debug purposes.

I agree with you that the success message can be misleading, especially when the majority of the data (from OneDrive) selected for backup has been omitted.