James_Walton
13 years agoLevel 4
0xe000fed1 - A failure occurred querying the Writer status.
Hi
My backup to tape job for a server running 4 Hyper-V VMs has suddenly started failing. I haven't changed any options in the backup job. Here is the full error (I don't have AOFO selected in the backup job so why is it throwing this error?):
Backup V-79-57344-65233 - AOFO: Initialization failure on: "VRTSRV::\\hostserver.domain.com\Hyper-V?Virtual?Machine\VM". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status. Check the Windows Event Viewer for details. Writer Name: Microsoft Hyper-V, Writer ID: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Waiting for backup complete notification (5).
This is then repeated for each of the 4 VMs on the server. This has failed twice in a row now.
This is seen in the event viewer:
Volume Shadow Copy Service error: Unexpected error calling routine IVssAsrWriterBackup::GetAsrMetadata. hr = 0x80042411, A critical volume selected for backup exists on a disk which cannot be backed up by ASR.
.
Operation:
PrepareForBackup event
Context:
Execution Context: ASR Writer
Execution Context: Writer
Writer Class Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Name: ASR Writer
Writer Instance ID: {d4d086f9-fed2-4844-895c-668a8aaf78dd}
Error-specific details:
Followed by:
Volume Shadow Copy Service warning: ASR writer Error 0x80042411. hr = 0x00000000, The operation completed successfully.
.
Operation:
PrepareForBackup event
Context:
Execution Context: ASR Writer
Execution Context: Writer
Writer Class Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Name: ASR Writer
Writer Instance ID: {d4d086f9-fed2-4844-895c-668a8aaf78dd}
Error-specific details:
Hi,
Run the following command from a command prompt: vssadmin list writers. Any writers not Stable and Running are in error, and you can normally get around this by restarting the server. If not, reregister the VSS *.dlls as per the TN below:
http://www.symantec.com/business/support/index?page=content&id=TECH70486
Thanks!