[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2950
  • Last Modified:

Symantec Backup Exec 2010 Errors While Backing Up MS Exchange; Final error: 0xe000fed1 - A failure occurred querying the Writer status.

I get and error when doing an Incremental backup of Exchange with Symantec Backup Exec 2010.

If I do a Full backup it will complete correctly but when I do an Incremental it fails immediately.

The server OS is SBS 2008

Below is the logged error

JOB COMPLETION STATUS:

Completed status: Failed
Final error: 0xe000fed1 - A failure occurred querying the Writer status.
Final error category: Resource Errors


ERRORS:

Backup- AGCSBS
V-79-57344-65233 - AOFO: Initialization failure on: "\\AGCSBS\Microsoft Information Store\First Storage Group". 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: Failed during prepare backup operation (7).

V-79-57344-65233 - AOFO: Initialization failure on: "\\AGCSBS\Microsoft Information Store\Second Storage Group". 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: Failed during prepare backup operation (7).
0
TechAK
Asked:
TechAK
1 Solution
 
Mkris9Commented:
In command prompt, type in vssadmin list writers

This will show you exactly which writer failed - in this case, VSS writer (plus something else, if there is).

Also normally a reboot fixes the issue.
0
 
DanMarCommented:
If none of this works try swapping to Symantec open file.
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
JarrodCommented:
Just out of curiousity is exchange in a vm ? Had an almost identical issue where I couldnt backup exchange at the vm level when I moved to backupexec 2010 from 12.5, I had to install the remote agent on the exchange server directly and backup the exchange server directly for my full and incrememntals to work. Hope this helps
0
 
Carol ChisholmCommented:
Have you rebooted the Exchange server?
0
 
TechAKAuthor Commented:
Exchange is not in a VM

I have rebooted several times

I ran vssadmin list writers and the following writer failed

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {5b1df0fe-b897-4422-9edb-ecc6e3fd5ac9}
   State: [7] Failed
   Last error: No error

I did find out that it only happens when performing an Incremental backup on Exchange. If I run a Full backup everything is fine if I run an Incremental backup I get the error and nobody can connect to Exchange until I reboot the system.
0
 
TechAKAuthor Commented:
Nothing helped
0
 
TechAKAuthor Commented:
Nothing worked
0

Featured Post

The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now