Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Failed Backup Jobs - 0XE000FED1: A Failure occurred querying the Writer Status

Created: 01 Jan 2014 • Updated: 04 Jan 2014 | 9 comments
This issue has been solved. See solution.

We're running Symantec Backup Exec 2010 R3 and Windows Server 2008 with Exchange 2010.

I've been unable to run an Exchange server backup and am constantly getting the error "A Failure occurred querying the Writer Status".

I've checked the VSSWriters on the exchange server in question and they are all Stable with no errors.

I scoured through the Symantec forums and haven't really come across any solutions for this error where all VSSWriters are stable with no errors.

Here is the error i'm getting from the Job History:

V-79-57344-65233 - AOFO: Initialization failure on: "\\EX-01.local\Microsoft Information Store\MailboxDB2". 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: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Waiting for backup complete notification (5).

V-79-57344-65233 - AOFO: Initialization failure on: "\\EX-01.local\Microsoft Information Store\MailboxDB3". 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: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Waiting for backup complete notification (5).

V-79-57344-65233 - AOFO: Initialization failure on: "\\EX-01.local\Microsoft Information Store\MailboxDB4". 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: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Waiting for backup complete notification (5).

Any ideas?

Operating Systems:

Comments 9 CommentsJump to latest comment

Sush...'s picture

Hello David,

     Try rebooting your Exchange server ones and then try the backups.

Regards,

-Sush...

Hope this piece of Information Helps you... and if it does then mark this response as Solution....!!!

SOLUTION
CraigV's picture

Hi,

Are you using Advanced Open File Option in your backup job? If so, turn it off as it isn't recommended for use with database backups.

Try the backup again and report back...if this works, then you can consider splitting your backups off from each other. Data backups use AOFO; database backups don't use AOFO.

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

Sush...'s picture

Hi CraigV,

    Just FYI,

  OP has Exchange 2010 on Win 2008... so irrelevant of AOFO is selected or not it is always going to use VSS for backups.

Regards,

-Sush...

Hope this piece of Information Helps you... and if it does then mark this response as Solution....!!!

CraigV's picture

Yes, I am well aware of that, but would you recommend then that the OP uses AOFO when backing up Exchange? Server 2003 also used VSS and I've been advised by Symantec technical support in the past NOT to use it...

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

Sush...'s picture

That was specific to Exchange 2003.....

http://www.symantec.com/docs/TECH44580  : Limitations of snapshot backup of Exchange 2003 databases

Regards,

-Sush...

Hope this piece of Information Helps you... and if it does then mark this response as Solution....!!!

Vishal Shinde's picture

additionally check for any relevant events/errors in the event viewer of your exchange server.

Regards,

Vishal

Vishal Shinde

Sr.Learning Consultant

Symantec Education Services

CraigV's picture

...what relevant errors?

The OP has checked the VSS writers on the Exchange server and they are stable.

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

Vishal Shinde's picture

Hello Craig,

in most of such cases, exchange specific errors are logged in the event viewer of the exchange server during the backup window.

Regards,

Vishal

Vishal Shinde

Sr.Learning Consultant

Symantec Education Services

DavidItlantian's picture

Thanks for all the input guys. We ended up just rebooting the exchange server because all other suggestions just didn't work.

Again Thanks for all the input.