Backup task execution failed - Acronis True Image notification

Robert, the logs show that there was a VSS snapshot error, so it is possible that this cleared itself over the time the backup was running.

May be worth running the Acronis VSS Doctor tool to see if that shows any issues?

Otherwise, doing a Windows restart may be worth doing if the system has been up for some time.

VSS Doctor ran OK (all green check marks) EXCEPT for:

==========================================================
Some VSS-related errors or warnings occurred during the previous day
==========================================================

The event log portion of the report is attached

I can, of course, reboot the system but before I do that is there anything else I should look at?

Robert, that is quite a lot of VSS related errors over a short period of time.  Have you tried following the SearchLink's provided in the report to see if that provides any more information?

Otherwise, I would be looking at a Windows restart then keep an eye for any further errors being reported / run the VSS Doctor before your next scheduled backups to check all is clear since the restart, then repeat again after the backup.

I decided to wait and see. The error might be "legitimate" in that something interfered with the backup. It did recover from the situation and eventually completed the scheduled backup and removed the error status from the "activity" list.

Time-out errors occur in Volume Shadow Copy service writers, and shadow copies are lost during backup and during times when there are high levels of input/output

I did "vssadmin list writers" as suggested but I was apparently too late for that to show anything.

I did do a restart just to be safe.

I'm having a similar problem, with the same "Backup task execution failed" message. Ran the VSS Doctor tool and "fixed" some of the errors it found. This backup is backing up my C: drive (windows 10) to a NAS with several TB of free disk space (so the target drive isn't a problem). The message I get when the backup fails seems to point to a file c:\bs_hudson\workspace\723\core\backup\file_writer.cpp:111 and several iterations of that basic folder.

Here's the pertinent text from the failure email:

| error 0x4001d: The quotas are violated.
| line: 0x6d93396f95de5cb
| file: c:\bs_hudson\workspace\723\core\backup\file_writer.cpp:111
| function: `anonymous-namespace'::FreeSpaceChecker::CheckFreeSpace
| line: 0x6d93396f95de5cb, c:\bs_hudson\workspace\723\core\backup\file_writer.cpp:111, `anonymous-namespace'::FreeSpaceChecker::CheckFreeSpace
| $module: ti_demon_vs_15470
2020-04-18T13:39:34:099-05:00 12048 E000101F6: Error 0x101f6: Write error
| trace level: error
| line: 0x65b5eb7011094700
| file: c:\bs_hudson\workspace\723\processor\diskadm\da_commit.cpp:345
| function: DaProcessor::CommitImpl::OnDaError
| line: 0x65b5eb7011094700, c:\bs_hudson\workspace\723\processor\diskadm\da_commit.cpp:345, DaProcessor::CommitImpl::OnDaError
| $module: ti_demon_vs_15470
|
| error 0x70004: Write error
| line: 0x9d2de1f088cbc4d8
| file: c:\bs_hudson\workspace\723\core\resizer\backup\stream_wrappers.cpp:64
| function: resizer::StreamWrapper::Write
| line: 0x9d2de1f088cbc4d8, c:\bs_hudson\workspace\723\core\resizer\backup\stream_wrappers.cpp:64, resizer::StreamWrapper::Write
| $module: ti_demon_vs_15470
|
| error 0x4001d: The quotas are violated.
| line: 0x1d8eab676a3f6aee
| file: c:\bs_hudson\workspace\723\products\imager\archive\impl\operations\archive_message_callback.cpp:1221
| function: TrueImage::Archive::ArchiveMsgWriteCallbackProcessor::ProcessWriteCallback
| line: 0x1d8eab676a3f6aee, c:\bs_hudson\workspace\723\products\imager\archive\impl\operations\archive_message_callback.cpp:1221, TrueImage::Archive::ArchiveMsgWriteCallbackProcessor::ProcessWriteCallback
| Path: \\NAS-4TBX2\NAS Drive 1\Drive C SSD backup via Acronis\Samsung SSD Backup to NAS-4TBX2_full_b1_s1_v1-3.tib
| $module: ti_demon_vs_15470
|
| error 0x4001d: The quotas are violated.
| line: 0x6d93396f95de5cb
| file: c:\bs_hudson\workspace\723\core\backup\file_writer.cpp:111
| function: `anonymous-namespace'::FreeSpaceChecker::CheckFreeSpace
| line: 0x6d93396f95de5cb, c:\bs_hudson\workspace\723\core\backup\file_writer.cpp:111, `anonymous-namespace'::FreeSpaceChecker::CheckFreeSpace
| $module: ti_demon_vs_15470
2020-04-18T13:40:11:211-05:00 12048 E013C0005: Error 0x13c0005: Operation has completed with errors.
| trace level: error
| line: 0x9f2c53c72e8bce5f
| file: c:\bs_hudson\workspace\723\products\imager\demon\main.cpp:617
| function: main
| line: 0x9f2c53c72e8bce5f, c:\bs_hudson\workspace\723\products\imager\demon\main.cpp:617, main
| $module: ti_demon_vs_15470

When I look for those folders on the C: drive, they don't exist (showing hidden folders); assume they have something to do with the Acronis backup process and get deleted after the error. 

Backup to an external also fails.

Any thoughts? 

Bob, the relevant entries from the log are:

| error 0x4001d: The quotas are violated.
| function: `anonymous-namespace'::FreeSpaceChecker::CheckFreeSpace
2020-04-18T13:39:34:099-05:00 12048 E000101F6: Error 0x101f6: Write error
| error 0x70004: Write error
| error 0x4001d: The quotas are violated.
| Path: \\NAS-4TBX2\NAS Drive 1\Drive C SSD backup via Acronis\Samsung SSD Backup to NAS-4TBX2_full_b1_s1_v1-3.tib
2020-04-18T13:40:11:211-05:00 12048 E013C0005: Error 0x13c0005: Operation has completed with errors.

Basically you have run out of free space for the backup to be written to your NAS.

Thanks, Steve. I'm changing the backup to a different drive with over 2.5 TB of free space and will see if that makes a difference. 

The problem was that the backup was mistakenly set to back up my entire system - way to much for any one NAS! I discovered my error, recreated a backup of just the C: drive, and everything worked smoothly. 

Good to hear that the issue is resolved - thanks for the feedback.