Backup Failing on Domain Controller/Virtual Machine Host
Web Console Error details:
Error
DATE AND TIME
Jan 14, 2019, 12:39:10 PM
MODULE
309
MESSAGE
Additional info:
------------------------
Error code: 22
Module: 309
LineInfo: 0x8D165E86FB81959B
Fields: {"$module":"service_process_vsa64_12210","CommandID":"8F01AC13-F59E-4851-9204-DE1FD77E36B4"}
Message: TOL: Failed to execute the command. Backing up
------------------------
Error code: 22
Module: 309
LineInfo: 0x8D165E86FB81959B
Fields: {"$module":"gtob_backup_command_addon_vsa64_12210","CommandID":"8F01AC13-F59E-4851-9204-DE1FD77E36B4"}
Message: TOL: Failed to execute the command. Backing up
------------------------
Error code: 252
Module: 161
LineInfo: 0x9FC3EE39511C2BD9
Fields: {"$module":"disk_bundle_vsa64_12210","account":"redacted"}
Message: Stream name: 'VMHaddress-037AC1F8-3F93-424D-9364-0C0DE4C572E5-FBB2AE1F-DAFA-407F-9CEE-31D0D102FB2FA.tibx'.
------------------------
Error code: 3
Module: 329
LineInfo: 0x1CD98AAE889424F9
Fields: {"$module":"disk_bundle_vsa64_12210"}
Message: Backup has failed.
------------------------
Error code: 1060
Module: 1
LineInfo: 0xB43E776571144DF0
Fields: {"$module":"disk_bundle_vsa64_12210"}
Message: Failed to commit operations.
------------------------
Error code: 33
Module: 7
LineInfo: 0x8BA4FA0BAC28BEAC
Fields: {"$module":"disk_bundle_vsa64_12210"}
Message: Failed to create volume snapshot.
------------------------
Error code: 50243
Module: 16
LineInfo: 0x3FEC04E376B8A16E
Fields: {"$module":"disk_bundle_vsa64_12210"}
Message: Failed to unlock the volume snapshot. To troubleshoot VSS issues, download and run Acronis VSS Doctor available at https://www.acronis.com/en-us/personal/vss-diagnostic-free-tool/
------------------------
Error code: 50281
Module: 16
LineInfo: 0x3FEC04E376B89DAF
Fields: {"$module":"disk_bundle_vsa64_12210"}
Message: VSS writer 'WIDWriter' with class ID '8D5194E1-E455-434A-B2E5-51296CCE67DF' has failed to process the snapshot. To troubleshoot VSS issues, download and run Acronis VSS Doctor available at https://www.acronis.com/en-us/personal/vss-diagnostic-free-tool/
------------------------
Error code: 65520
Module: 0
LineInfo: 0xBD28FDBD64EDB8FB
Fields: {"$module":"disk_bundle_vsa64_12210","code":"2147754996"}
Message:
VSS Doctor details:
VSS Writers Status:
WIDWriter: [8] Failed, Non-retryable errorEvent Log:
A VSS writer has rejected an event with error 0c800423f4, The writer experienced a non-transient error. If the backup process is retried, the error is likely to reoccur.. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer. Operation: PrepareForSnapshot Event Context: Execution Context: Writer Writer Class Id: {8d5194e1-r455-434a-b2e5-51296ccce67fd} Writer Name: WIDWriter Writer Instance Name: SQL Server Code-Named 'Denali' CTP2:SQLWriter Writer Instance ID: {d2641b15-cac0-4503-902c-a82e1ab81b66} Command Line: C:\Windows\WID\Binn\sqlwriter.exe -w Process ID: 15732
Trying switching to Microsoft VSS provider.
Edit: No luck on MS VSS provider either.
I don't think I have any applications using WID, so will try removing/reinstalling this feature and try again.
Will update.
Uninstalling the Windows Internal Directory feature from the server worked!
Hi Samuel,
thanks for sharing the results! We are glad that the issue is resolved.
Hello Samuel,
On Jan 1st, of this year, Acronis Backup 12.5 quit backing our our AD/DC primary server, and with the same error.
I've been waiting on a resolution for this issue since then.
I've been working with a few techs, they supposedly escalated the ticket higher up the chain.
Today a technician responded to me saying that the issue was caused by .... 'packet loss'
That our network was not sufficient, or had too much 'packet loss'...
As soon as I heard this I lost all faith, absolutely lost all faith in Acronis.
Below is their response.. maybe it'll help you??? If you come up with anything would you please share? I'm at a loss and it's very troubling that Acronis is now pushing the issue off on Cisco hardware that works perfectly, or as close to perfection as possible.
My name is Daniel. I’m an Expert Support Engineer in Acronis Support Team I’m taking over the Case 03575586 I’ll be glad to help you.
As far as I understand the issue is in start of automatic backup plans.
Please feel free to correct me if I’m wrong.
After provided log files investigation I can state that the issue is caused by network issue:
1. Such linetags in errors are connected to network issues.
2. Wireshark log shows huge amount of packets loss between 192.168.200.216 (SV-ESKO01) and 192.168.200.250 (NAS)
The issue might be caused by connection itself, by NIC driver, by managed switch etc.
I recommend you to check all network chain between SV-ESKO01 machine and NAS.
Please let me know if this helped to resolve the issue.
If you have any additional questions feel free to contact me.
--
Best regards,Daniil Yakorev, Support Engineer, Acronis Customer Central
Hey David, check my resolution above. If you're getting the exact same error, where it's failing on the WID VSS Writer and you are absolutely positive you don't have any features installed on the server that require WID, uninstall the feature and restart and try backing up again.
Hello David,
according to the logs in your case, the root cause of the issue is OS Error 665, which is according to net helpmsg command is a filesystem limitation.
There could be two possible solutions. The first one is described in this KB article you should set Splitting in Backup Options. The second one is to select Version 11 backup format in Backup Options.
In both variants you will need to create a new backup archive with the changes in Backup Options described above..
Hello Maria,
Thank you so much for the info. I’ll read the KB and look into splitting the backup.
The funny thing, actually two things, is the this issue started on exactly Jan 1st. The last backup that ran was on Dec 31st, 2018.
The backups failed, each time, after that but only on two of our servers. Our main AD/DC and a very highly loaded graphics processor server.
Both of them Windows 2008R2 and both have been backing up perfectly up till Jan 1st. No changes were made on new years eve and I don’t even think any windows updates were installed, automatically or manually.
The second thing that I thought was funny was that the Acronis tech actually thinks it’s a network hardware issue with the NIC.
Well, thank you so much for your help. I'm going to cross my fingers :)
Hello David,
how is the progress with backup?
Please note that if you selected Version 12 backup format , then all incremental backups that depend on the first full one are saved to a single .tibx file. Since you mentioned that this is a highly loaded graphics processor server, thus, it's backup file weights pretty much, plus it has been continually growing (with incremental slices) and reached the critical size one day which caused the above error.