Skip to main content

Backing up Shares are failing after a few days of running succesfully - Acronis Backup 12

Thread needs solution

SBS 2011 Standard that does Active Directory and Exchange virtualized on Hyper V host

-the backup job I have setup is simply doing file shares on C:, backups to a network share to another device on the network

-backups will run successfully for a few days, but will start failing after 4-5 days of running successfully regardless of the day of the week

-I have been able to temporarily correct issue by moving backup files to a different location and letting the job run a new full backup, will then run for a few days with incremental backups then start failing.

I have attached the logs from the past two days of the most recent failures. Was hoping someone could take a quick look at the gibberish below to see if the spot something glaringly obvious that is wrong, let me know if you may need any other information.

NOV 27th log first failure that ran from 7PM to 430 AM

2017-11-27T19:00:13:404-06:00 23716 I0135003A: User is running command. Command=Backup plan 'SBS Shares Backup'; User=; clientProfileID=; clientSessionID=4760CE0B-CAB8-4B65-9DD0-CEF2D5BFE3C1
2017-11-27T19:01:24:791-06:00 25168 I0135003A: User is running command. Command=Backing up; User=; clientProfileID=; clientSessionID=4760CE0B-CAB8-4B65-9DD0-CEF2D5BFE3C1
2017-11-27T19:01:25:295-06:00 25168 I00000000: I00000000: Backup Inclusions list:

2017-11-27T19:01:25:328-06:00 25168 I00000000: I00000000: Client Proposals

2017-11-27T19:01:25:335-06:00 25168 I00000000: I00000000: Design

2017-11-27T19:01:25:357-06:00 25168 I00000000: I00000000: Private Heartland

2017-11-27T19:01:25:458-06:00 25168 I00000000: I00000000: Private

2017-11-27T19:01:25:468-06:00 25168 I00000000: I00000000: Private2

2017-11-27T19:01:25:487-06:00 25168 I00000000: I00000000: SCANS

2017-11-27T19:01:25:505-06:00 25168 I00000000: I00000000: SHARED2

2017-11-27T19:01:25:528-06:00 25168 I00000000: I00000000: StorageReports

2017-11-27T19:01:25:568-06:00 25168 I00000000: I00000000: private operations

2017-11-27T19:01:25:582-06:00 25168 I00000000: I00000000: Archive: //storage01/ACRONIS/\SBS.alternative.local-CCFCAC01-1FEC-4607-A6B2-40E85025ED21-EB7B4521-FD5E-482A-A857-EB4EE481AF54A

2017-11-27T19:01:48:695-06:00 25168 I00000000: Using ar_io_local to open '\\storage01\ACRONIS\' with token 0000000000000DE4
2017-11-27T19:01:49:528-06:00 25168 I00000000: Create Full Backup From C:\Client Proposals\...To file file://storage01/ACRONIS/SBS.alternative.local-CCFCAC01-1FEC-4607-A6B2-40E85025ED21-EB7B4521-FD5E-482A-A857-EB4EE481AF54A.tibxCompression NormalExclude Files matching maskMatch criterion *\System Volume Information\*{3808876B-C176-4e48-B7AE-04046E6CC752}; ...Ask for the first media No
2017-11-27T19:02:50:112-06:00 25168 I000101FA: Locking partition C:...
2017-11-28T04:31:53:409-06:00 25168 E00040019: Error 0x40019: Unknown error occurred while backing up.
| trace level: error
| channel: tol-activity#85E77CF5-9BE9-4D12-BC4F-FFA46ED0568B
| line: 0xba19e88dc5fea1ae
| file: k:\15\processor\backup\backup_file.cpp:1109
| function: DaProcessor::Backup::_DoFileOperation
| $module: disk_bundle_vsa64_7970
|
| error 0x40019: Error occurred while backing up.
| line: 0x5f25c37074a54483
| file: k:\15\processor\backup\archive3_file_backup.cpp:818
| function: `anonymous-namespace'::Archive3FileBackupBuilder::Write
| Archive3Code: 0x13ec
| Name: SBS.alternative.local-CCFCAC01-1FEC-4607-A6B2-40E85025ED21-EB7B4521-FD5E-482A-A857-EB4EE481AF54A.tibx
| $module: archive3_adapter_vsa64_7970
2017-11-28T04:32:11:209-06:00 25168 E0135003D: Error 0x135003d: Command has failed. Command=Backing up;
| trace level: error
| channel: tol-activity#85E77CF5-9BE9-4D12-BC4F-FFA46ED0568B
| line: 0x4a8728dc8a1c95a1
| file: k:\15\enterprise\common\tol\gating_activity.cpp:251
| function: Tol::`anonymous-namespace'::BusinessActivityTracker::OnCompleted
| $module: service_process_vsa64_7970
|
| error 0x1350016: TOL: Failed to execute the command. Backing up
| line: 0x8d165e86fb81959b
| file: k:\15\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 8F01AC13-F59E-4851-9204-DE1FD77E36B4
| $module: service_process_vsa64_7970
|
| error 0x1350016: TOL: Failed to execute the command. Backing up
| line: 0x8d165e86fb81959b
| file: k:\15\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 8F01AC13-F59E-4851-9204-DE1FD77E36B4
| $module: gtob_backup_command_addon_vsa64_7970
|
| error 0x1490003: Backup has failed.
| line: 0x1cd98aae889424f9
| file: k:\15\enterprise\managers\gtob\util\impl\convert_batch_result.cpp:58
| function: Gtob::Backup::ConvertBatchResult
| $module: disk_bundle_vsa64_7970
|
| error 0x10424
| line: 0xba19e88dc5fea1b0
| file: k:\15\processor\backup\backup_file.cpp:1111
| function: DaProcessor::Backup::_DoFileOperation
| $module: disk_bundle_vsa64_7970
|
| error 0x40019: Unknown error occurred while backing up.
| line: 0xba19e88dc5fea1ae
| file: k:\15\processor\backup\backup_file.cpp:1109
| function: DaProcessor::Backup::_DoFileOperation
| $module: disk_bundle_vsa64_7970
|
| error 0x40019: Error occurred while backing up.
| line: 0x5f25c37074a54483
| file: k:\15\processor\backup\archive3_file_backup.cpp:818
| function: `anonymous-namespace'::Archive3FileBackupBuilder::Write
| Archive3Code: 0x13ec
| Name: SBS.alternative.local-CCFCAC01-1FEC-4607-A6B2-40E85025ED21-EB7B4521-FD5E-482A-A857-EB4EE481AF54A.tibx
| $module: archive3_adapter_vsa64_7970
2017-11-28T04:32:13:620-06:00 23716 E01350016: Error 0x1350016: TOL: Failed to execute the command. Backing up
| trace level: error
| channel: tol-activity#E07069AA-D69A-4C39-862B-8F59BC0C099C
| line: 0x8d165e86fb81959b
| file: k:\15\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 8F01AC13-F59E-4851-9204-DE1FD77E36B4
| $module: service_process_vsa64_7970
|
| error 0x1350016: TOL: Failed to execute the command. Backing up
| line: 0x8d165e86fb81959b
| file: k:\15\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 8F01AC13-F59E-4851-9204-DE1FD77E36B4
| $module: gtob_backup_command_addon_vsa64_7970
|
| error 0x1490003: Backup has failed.
| line: 0x1cd98aae889424f9
| file: k:\15\enterprise\managers\gtob\util\impl\convert_batch_result.cpp:58
| function: Gtob::Backup::ConvertBatchResult
| $module: disk_bundle_vsa64_7970
|
| error 0x10424
| line: 0xba19e88dc5fea1b0
| file: k:\15\processor\backup\backup_file.cpp:1111
| function: DaProcessor::Backup::_DoFileOperation
| $module: disk_bundle_vsa64_7970
|
| error 0x40019: Unknown error occurred while backing up.
| line: 0xba19e88dc5fea1ae
| file: k:\15\processor\backup\backup_file.cpp:1109
| function: DaProcessor::Backup::_DoFileOperation
| $module: disk_bundle_vsa64_7970
|
| error 0x40019: Error occurred while backing up.
| line: 0x5f25c37074a54483
| file: k:\15\processor\backup\archive3_file_backup.cpp:818
| function: `anonymous-namespace'::Archive3FileBackupBuilder::Write
| Archive3Code: 0x13ec
| Name: SBS.alternative.local-CCFCAC01-1FEC-4607-A6B2-40E85025ED21-EB7B4521-FD5E-482A-A857-EB4EE481AF54A.tibx
| $module: archive3_adapter_vsa64_7970
2017-11-28T04:32:13:628-06:00 23716 E01350016: Error 0x1350016: TOL: Failed to execute the command. Backup workflow
| trace level: error
| channel: tol-activity#E07069AA-D69A-4C39-862B-8F59BC0C099C
| line: 0x8d165e86fb81959b
| file: k:\15\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: F30407D6-601F-11E0-9C67-FF46DFD72085
| $module: mms_vsa64_7970
|
| error 0x1350016: TOL: Failed to execute the command. Backup workflow
| line: 0x8d165e86fb81959b
| file: k:\15\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: F30407D6-601F-11E0-9C67-FF46DFD72085
| $module: gtob_backup_command_addon_vsa64_7970
|
| error 0x1490002: Step 'Backup' has failed.
| line: 0x8edc81ea38faba77
| file: k:\15\enterprise\managers\gtob\backupers\backup_command\impl\backup_workflow_command.cpp:619
| function: `anonymous-namespace'::BackupWorkflowCommand::ProcessWorkflowSteps
| TraceLevel: 0x1
| StepType: 0x2
| $module: gtob_backup_command_addon_vsa64_7970
|
| error 0x1350016: TOL: Failed to execute the command. Tol::IsolateCommand
| line: 0x8d165e86fb81959b
| file: k:\15\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 4504F8D4-2727-42AB-BB4F-A42EDBB790A0
| $module: mms_vsa64_7970
|
| error 0x1350016: TOL: Failed to execute the command. Backing up
| line: 0x8d165e86fb81959b
| file: k:\15\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 8F01AC13-F59E-4851-9204-DE1FD77E36B4
| $module: service_process_vsa64_7970
|
| error 0x1350016: TOL: Failed to execute the command. Backing up
| line: 0x8d165e86fb81959b
| file: k:\15\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 8F01AC13-F59E-4851-9204-DE1FD77E36B4
| $module: gtob_backup_command_addon_vsa64_7970
|
| error 0x1490003: Backup has failed.
| line: 0x1cd98aae889424f9
| file: k:\15\enterprise\managers\gtob\util\impl\convert_batch_result.cpp:58
| function: Gtob::Backup::ConvertBatchResult
| $module: disk_bundle_vsa64_7970
|
| error 0x10424
| line: 0xba19e88dc5fea1b0
| file: k:\15\processor\backup\backup_file.cpp:1111
| function: DaProcessor::Backup::_DoFileOperation
| $module: disk_bundle_vsa64_7970
|
| error 0x40019: Unknown error occurred while backing up.
| line: 0xba19e88dc5fea1ae
| file: k:\15\processor\backup\backup_file.cpp:1109
| function: DaProcessor::Backup::_DoFileOperation
| $module: disk_bundle_vsa64_7970
|
| error 0x40019: Error occurred while backing up.
| line: 0x5f25c37074a54483
| file: k:\15\processor\backup\archive3_file_backup.cpp:818
| function: `anonymous-namespace'::Archive3FileBackupBuilder::Write
| Archive3Code: 0x13ec
| Name: SBS.alternative.local-CCFCAC01-1FEC-4607-A6B2-40E85025ED21-EB7B4521-FD5E-482A-A857-EB4EE481AF54A.tibx
| $module: archive3_adapter_vsa64_7970
2017-11-28T04:32:13:889-06:00 23716 E0135003D: Error 0x135003d: Command has failed. Command=Backup plan 'SBS Shares Backup';
| trace level: error
| channel: tol-activity#E07069AA-D69A-4C39-862B-8F59BC0C099C
| line: 0x4a8728dc8a1c95a1
| file: k:\15\enterprise\common\tol\gating_activity.cpp:251
| function: Tol::`anonymous-namespace'::BusinessActivityTracker::OnCompleted
| $module: mms_vsa64_7970
|
| error 0x1350016: TOL: Failed to execute the command. Backup plan 'SBS Shares Backup'
| line: 0x8d165e86fb81959b
| file: k:\15\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: D332948D-A7A9-4E07-B76C-253DCF6E17FB
| $module: mms_vsa64_7970
|
| error 0x1350016: TOL: Failed to execute the command. Backup plan 'SBS Shares Backup'
| line: 0x8d165e86fb81959b
| file: k:\15\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: D332948D-A7A9-4E07-B76C-253DCF6E17FB
| $module: agent_protection_addon_vsa64_7970
|
| error 0x1330029: Failed to execute the command.
| line: 0xe6792a5ee190de2c
| file: k:\15\enterprise\managers\gtob\protection\agent_engine\protect_command.cpp:218
| function: `anonymous-namespace'::ProtectCommand::SafeExecute
| $module: agent_protection_addon_vsa64_7970
|
| error 0x1350035: 2 activities have not succeeded. One of them is displayed.
| line: 0x2e7e9e174f1fb719
| file: k:\15\enterprise\common\tol\replica\event_processor.cpp:110
| function: Tol::`anonymous-namespace'::CreateCumulativeError
| FailCount: 0x2
| $module: agent_protection_addon_vsa64_7970
|
| error 0x1350016: TOL: Failed to execute the command. Backing up
| line: 0x8d165e86fb81959b
| file: k:\15\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 8F01AC13-F59E-4851-9204-DE1FD77E36B4
| $module: service_process_vsa64_7970
|
| error 0x1350016: TOL: Failed to execute the command. Backing up
| line: 0x8d165e86fb81959b
| file: k:\15\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 8F01AC13-F59E-4851-9204-DE1FD77E36B4
| $module: gtob_backup_command_addon_vsa64_7970
|
| error 0x1490003: Backup has failed.
| line: 0x1cd98aae889424f9
| file: k:\15\enterprise\managers\gtob\util\impl\convert_batch_result.cpp:58
| function: Gtob::Backup::ConvertBatchResult
| $module: disk_bundle_vsa64_7970
|
| error 0x10424
| line: 0xba19e88dc5fea1b0
| file: k:\15\processor\backup\backup_file.cpp:1111
| function: DaProcessor::Backup::_DoFileOperation
| $module: disk_bundle_vsa64_7970
|
| error 0x40019: Unknown error occurred while backing up.
| line: 0xba19e88dc5fea1ae
| file: k:\15\processor\backup\backup_file.cpp:1109
| function: DaProcessor::Backup::_DoFileOperation
| $module: disk_bundle_vsa64_7970
|
| error 0x40019: Error occurred while backing up.
| line: 0x5f25c37074a54483
| file: k:\15\processor\backup\archive3_file_backup.cpp:818
| function: `anonymous-namespace'::Archive3FileBackupBuilder::Write
| Archive3Code: 0x13ec
| Name: SBS.alternative.local-CCFCAC01-1FEC-4607-A6B2-40E85025ED21-EB7B4521-FD5E-482A-A857-EB4EE481AF54A.tibx
| $module: archive3_adapter_vsa64_7970

Nov 28th backup job ran from 7PM to 706PM

2017-11-28T19:00:13:620-06:00 18756 I0135003A: User is running command. Command=Backup plan 'SBS Shares Backup'; User=; clientProfileID=; clientSessionID=B80156DB-6F42-4BB1-BAA1-E11595E162FD
2017-11-28T19:01:24:607-06:00 27588 I0135003A: User is running command. Command=Backing up; User=; clientProfileID=; clientSessionID=B80156DB-6F42-4BB1-BAA1-E11595E162FD
2017-11-28T19:01:25:272-06:00 27588 I00000000: I00000000: Backup Inclusions list:

2017-11-28T19:01:25:297-06:00 27588 I00000000: I00000000: Client Proposals

2017-11-28T19:01:25:331-06:00 27588 I00000000: I00000000: Design

2017-11-28T19:01:25:566-06:00 27588 I00000000: I00000000: Private Heartland

2017-11-28T19:01:25:581-06:00 27588 I00000000: I00000000: Private

2017-11-28T19:01:25:615-06:00 27588 I00000000: I00000000: Private2

2017-11-28T19:01:25:632-06:00 27588 I00000000: I00000000: SCANS

2017-11-28T19:01:25:673-06:00 27588 I00000000: I00000000: SHARED2

2017-11-28T19:01:25:695-06:00 27588 I00000000: I00000000: StorageReports

2017-11-28T19:01:25:703-06:00 27588 I00000000: I00000000: private operations

2017-11-28T19:01:25:742-06:00 27588 I00000000: I00000000: Archive: //storage01/ACRONIS/\SBS.alternative.local-CCFCAC01-1FEC-4607-A6B2-40E85025ED21-EB7B4521-FD5E-482A-A857-EB4EE481AF54A

2017-11-28T19:01:39:754-06:00 27588 I00000000: Using ar_io_local to open '\\storage01\ACRONIS\' with token 0000000000000DC8
2017-11-28T19:06:41:433-06:00 27588 E0135003D: Error 0x135003d: Command has failed. Command=Backing up;
| trace level: error
| channel: tol-activity#6BFDB4FB-B539-4ACF-9FEF-76969AB3403E
| line: 0x4a8728dc8a1c95a1
| file: k:\15\enterprise\common\tol\gating_activity.cpp:251
| function: Tol::`anonymous-namespace'::BusinessActivityTracker::OnCompleted
| $module: service_process_vsa64_7970
|
| error 0x1350016: TOL: Failed to execute the command. Backing up
| line: 0x8d165e86fb81959b
| file: k:\15\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 8F01AC13-F59E-4851-9204-DE1FD77E36B4
| $module: service_process_vsa64_7970
|
| error 0x1350016: TOL: Failed to execute the command. Backing up
| line: 0x8d165e86fb81959b
| file: k:\15\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 8F01AC13-F59E-4851-9204-DE1FD77E36B4
| $module: gtob_backup_command_addon_vsa64_7970
|
| error 0x1490003: Backup has failed.
| line: 0x1cd98aae889424f9
| file: k:\15\enterprise\managers\gtob\util\impl\convert_batch_result.cpp:58
| function: Gtob::Backup::ConvertBatchResult
| $module: disk_bundle_vsa64_7970
|
| error 0x10424: Failed to prepare an operation.
| line: 0x145a191bfe9050c3
| file: k:\15\processor\batch\batch.cpp:110
| function: Processor::BatchOperation::Execute
| $module: disk_bundle_vsa64_7970
|
| error 0x40007: Error occurred while opening the file.
| line: 0xc3bc4c1eb2299aec
| file: k:\15\enterprise\applications\archiving\storages\archive3\src\archive3.cpp:322
| function: `anonymous-namespace'::OpenArchive
| Archive3Code: 0x1399
| Name: SBS.alternative.local-CCFCAC01-1FEC-4607-A6B2-40E85025ED21-EB7B4521-FD5E-482A-A857-EB4EE481AF54A.tibx
| $module: archive3_adapter_vsa64_7970
|
| error 0x40015: Network disconnected.
| line: 0xc8d8731ce106f9df
| file: k:\13\archive\ver3\adapter\error.cpp:81
| function: `anonymous-namespace'::ConvertArchive3Error
| $module: archive3_adapter_vsa64_7970
2017-11-28T19:06:43:125-06:00 18756 E01350016: Error 0x1350016: TOL: Failed to execute the command. Backing up
| trace level: error
| channel: tol-activity#B83F4D03-4584-40AE-AA0C-F16E8545389B
| line: 0x8d165e86fb81959b
| file: k:\15\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 8F01AC13-F59E-4851-9204-DE1FD77E36B4
| $module: service_process_vsa64_7970
|
| error 0x1350016: TOL: Failed to execute the command. Backing up
| line: 0x8d165e86fb81959b
| file: k:\15\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 8F01AC13-F59E-4851-9204-DE1FD77E36B4
| $module: gtob_backup_command_addon_vsa64_7970
|
| error 0x1490003: Backup has failed.
| line: 0x1cd98aae889424f9
| file: k:\15\enterprise\managers\gtob\util\impl\convert_batch_result.cpp:58
| function: Gtob::Backup::ConvertBatchResult
| $module: disk_bundle_vsa64_7970
|
| error 0x10424: Failed to prepare an operation.
| line: 0x145a191bfe9050c3
| file: k:\15\processor\batch\batch.cpp:110
| function: Processor::BatchOperation::Execute
| $module: disk_bundle_vsa64_7970
|
| error 0x40007: Error occurred while opening the file.
| line: 0xc3bc4c1eb2299aec
| file: k:\15\enterprise\applications\archiving\storages\archive3\src\archive3.cpp:322
| function: `anonymous-namespace'::OpenArchive
| Archive3Code: 0x1399
| Name: SBS.alternative.local-CCFCAC01-1FEC-4607-A6B2-40E85025ED21-EB7B4521-FD5E-482A-A857-EB4EE481AF54A.tibx
| $module: archive3_adapter_vsa64_7970
|
| error 0x40015: Network disconnected.
| line: 0xc8d8731ce106f9df
| file: k:\13\archive\ver3\adapter\error.cpp:81
| function: `anonymous-namespace'::ConvertArchive3Error
| $module: archive3_adapter_vsa64_7970
2017-11-28T19:06:43:133-06:00 18756 E01350016: Error 0x1350016: TOL: Failed to execute the command. Backup workflow
| trace level: error
| channel: tol-activity#B83F4D03-4584-40AE-AA0C-F16E8545389B
| line: 0x8d165e86fb81959b
| file: k:\15\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: F30407D6-601F-11E0-9C67-FF46DFD72085
| $module: mms_vsa64_7970
|
| error 0x1350016: TOL: Failed to execute the command. Backup workflow
| line: 0x8d165e86fb81959b
| file: k:\15\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: F30407D6-601F-11E0-9C67-FF46DFD72085
| $module: gtob_backup_command_addon_vsa64_7970
|
| error 0x1490002: Step 'Backup' has failed.
| line: 0x8edc81ea38faba77
| file: k:\15\enterprise\managers\gtob\backupers\backup_command\impl\backup_workflow_command.cpp:619
| function: `anonymous-namespace'::BackupWorkflowCommand::ProcessWorkflowSteps
| TraceLevel: 0x1
| StepType: 0x2
| $module: gtob_backup_command_addon_vsa64_7970
|
| error 0x1350016: TOL: Failed to execute the command. Tol::IsolateCommand
| line: 0x8d165e86fb81959b
| file: k:\15\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 4504F8D4-2727-42AB-BB4F-A42EDBB790A0
| $module: mms_vsa64_7970
|
| error 0x1350016: TOL: Failed to execute the command. Backing up
| line: 0x8d165e86fb81959b
| file: k:\15\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 8F01AC13-F59E-4851-9204-DE1FD77E36B4
| $module: service_process_vsa64_7970
|
| error 0x1350016: TOL: Failed to execute the command. Backing up
| line: 0x8d165e86fb81959b
| file: k:\15\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 8F01AC13-F59E-4851-9204-DE1FD77E36B4
| $module: gtob_backup_command_addon_vsa64_7970
|
| error 0x1490003: Backup has failed.
| line: 0x1cd98aae889424f9
| file: k:\15\enterprise\managers\gtob\util\impl\convert_batch_result.cpp:58
| function: Gtob::Backup::ConvertBatchResult
| $module: disk_bundle_vsa64_7970
|
| error 0x10424: Failed to prepare an operation.
| line: 0x145a191bfe9050c3
| file: k:\15\processor\batch\batch.cpp:110
| function: Processor::BatchOperation::Execute
| $module: disk_bundle_vsa64_7970
|
| error 0x40007: Error occurred while opening the file.
| line: 0xc3bc4c1eb2299aec
| file: k:\15\enterprise\applications\archiving\storages\archive3\src\archive3.cpp:322
| function: `anonymous-namespace'::OpenArchive
| Archive3Code: 0x1399
| Name: SBS.alternative.local-CCFCAC01-1FEC-4607-A6B2-40E85025ED21-EB7B4521-FD5E-482A-A857-EB4EE481AF54A.tibx
| $module: archive3_adapter_vsa64_7970
|
| error 0x40015: Network disconnected.
| line: 0xc8d8731ce106f9df
| file: k:\13\archive\ver3\adapter\error.cpp:81
| function: `anonymous-namespace'::ConvertArchive3Error
| $module: archive3_adapter_vsa64_7970
2017-11-28T19:06:43:275-06:00 18756 E0135003D: Error 0x135003d: Command has failed. Command=Backup plan 'SBS Shares Backup';
| trace level: error
| channel: tol-activity#B83F4D03-4584-40AE-AA0C-F16E8545389B
| line: 0x4a8728dc8a1c95a1
| file: k:\15\enterprise\common\tol\gating_activity.cpp:251
| function: Tol::`anonymous-namespace'::BusinessActivityTracker::OnCompleted
| $module: mms_vsa64_7970
|
| error 0x1350016: TOL: Failed to execute the command. Backup plan 'SBS Shares Backup'
| line: 0x8d165e86fb81959b
| file: k:\15\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: D332948D-A7A9-4E07-B76C-253DCF6E17FB
| $module: mms_vsa64_7970
|
| error 0x1350016: TOL: Failed to execute the command. Backup plan 'SBS Shares Backup'
| line: 0x8d165e86fb81959b
| file: k:\15\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: D332948D-A7A9-4E07-B76C-253DCF6E17FB
| $module: agent_protection_addon_vsa64_7970
|
| error 0x1330029: Failed to execute the command.
| line: 0xe6792a5ee190de2c
| file: k:\15\enterprise\managers\gtob\protection\agent_engine\protect_command.cpp:218
| function: `anonymous-namespace'::ProtectCommand::SafeExecute
| $module: agent_protection_addon_vsa64_7970
|
| error 0x1350035: 2 activities have not succeeded. One of them is displayed.
| line: 0x2e7e9e174f1fb719
| file: k:\15\enterprise\common\tol\replica\event_processor.cpp:110
| function: Tol::`anonymous-namespace'::CreateCumulativeError
| FailCount: 0x2
| $module: agent_protection_addon_vsa64_7970
|
| error 0x1350016: TOL: Failed to execute the command. Backing up
| line: 0x8d165e86fb81959b
| file: k:\15\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 8F01AC13-F59E-4851-9204-DE1FD77E36B4
| $module: service_process_vsa64_7970
|
| error 0x1350016: TOL: Failed to execute the command. Backing up
| line: 0x8d165e86fb81959b
| file: k:\15\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 8F01AC13-F59E-4851-9204-DE1FD77E36B4
| $module: gtob_backup_command_addon_vsa64_7970
|
| error 0x1490003: Backup has failed.
| line: 0x1cd98aae889424f9
| file: k:\15\enterprise\managers\gtob\util\impl\convert_batch_result.cpp:58
| function: Gtob::Backup::ConvertBatchResult
| $module: disk_bundle_vsa64_7970
|
| error 0x10424: Failed to prepare an operation.
| line: 0x145a191bfe9050c3
| file: k:\15\processor\batch\batch.cpp:110
| function: Processor::BatchOperation::Execute
| $module: disk_bundle_vsa64_7970
|
| error 0x40007: Error occurred while opening the file.
| line: 0xc3bc4c1eb2299aec
| file: k:\15\enterprise\applications\archiving\storages\archive3\src\archive3.cpp:322
| function: `anonymous-namespace'::OpenArchive
| Archive3Code: 0x1399
| Name: SBS.alternative.local-CCFCAC01-1FEC-4607-A6B2-40E85025ED21-EB7B4521-FD5E-482A-A857-EB4EE481AF54A.tibx
| $module: archive3_adapter_vsa64_7970
|
| error 0x40015: Network disconnected.
| line: 0xc8d8731ce106f9df
| file: k:\13\archive\ver3\adapter\error.cpp:81
| function: `anonymous-namespace'::ConvertArchive3Error
| $module: archive3_adapter_vsa64_7970

 

 

Attachment Size
Nov 27.zip 2.51 KB
Nov 28.zip 2.31 KB
0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi,

The problem is related to new backup format (version 12) which in some cases is uncapable for handling intermittent network dropouts, which in conjunction with SMB service provided by specific NAS devices may produce failures to read the archive to append incremental changes. Most of these problems are addressed in the upcoming Update 2 for Acronis Backup 12.5 which we plan to release during the next week. In this update there is also resumable backup feature implemented for backup format version 12, where failed backups can be re-started to resume writing data to backup storage, while re-using the partial data which was uploaded during failed attempt.

Therefore I'd recommended the following: 1) Update the product to Update 2 build once it's out 2) As a workaround use backup format version 11: create a new backup plan -> Backup Options->Backup format->set to "version 11".

Thank you.

In reply to by truwrikodrorow…

Thank you so much! I will implement the work around and update when the update is available. I will be sure to post updates of the issue!

 

So I created a new back job with the backup format as version 11, but still got errors. I have reached out to support and it seems like the issues lies with the "Microsoft Exchange Writer" stuck on retryable error. I am going to have to look more into the Writer for Exchange to see if it is an issue with Exchange, or if Acronis is causing the errors with the Exchange VSS writer. Will keep updating this post with what a find out on my own and with Acronis Support.

So we are still troubleshooting the Exchange VSS writer, it is getting to the point where we are thinking of scrapping the mail server for more reasons than the backup issues. We are no longer getting failed backups, just the following warning:

Failed to start creating the volume snapshot.
Windows error: (0x800423F3) VSS writer 'Microsoft Exchange Writer' with class ID '76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7' has failed to process the snapshot.

Quite a few of the vss writers are "Waiting for Complettion". We are going to propose Office 365/Exchange Online solution shortly, as we are having these backup issues, spam issues, and compatibility with iOS issues.

 

I have considered trying out the VM Replication backup options, hoping maybe that would ignore any vss writer issues as we are working with a virtualized environment. Just need to do a bit of looking into before implementation.

 

Thanks for the help!

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Brandon,

One tip which may be helpful: despite Exchange VSS writers are failing, you can still back up this system if you disable "Application protection" option in the backup plan + disable "VSS for Physical/Virtual Machines" option (depends on whether you use agent-less or agent-based backup of the affected machine) - this would at least allow you to capture the entire system image, though without possibility to restore Exchange items from this backup (still you will be able to recover entire .edb Exchange database files).

VM replication will also be affected by VSS processing problems if you leave "VSS for Virtual Machines" backup option enabled, while from hypervisor side quiesced snapshot (with Quiesced=ON, memory=OFF parameters) still fails.

Thank you.

I have since turned of file level-backup snapshot and have no errors since. From my understanding the backups should be good just not time consistent.

Can anyone elaborate on any negative consequences for the changes I have made?

We are moving forward with switching to Exchange Online hosted email instead of internally hosted Exchange 2010, I believe this would 100% solve our backups issue as it is the Microsoft Exchange Writer that is constantly giving us errors.

Attachment Size
434039-141644.PNG 12.38 KB
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi,

The "File-level backup snapshot" option triggers VSS snapshot when enabled - this is done to ensure consistency of data within the snapshot (flush pending I/O to disk). If you perform files/folders backup with this option disabled, then the files opened for exclusive access by other applications won't be backed up properly - there will be corresponding warning thrown in the log file with reference to such file.

Thank you.