cancel
Showing results for 
Search instead for 
Did you mean: 

Problem to backup some Exchange 2007 servers with BackupExe 12

johnez
Level 2

Hi!

We are evaluating backupexe 12 to use for backing up a lot of exchange servers.

We are now testing at 7 different exchange servers (2003 and 2007). We have problem with several exchange 2007 servers. They are running on Windows 2003 R2 with SP2

 

The error in backup exe is:

Job ended: den 9 april 2008 at 10:22:53
Completed status: Failed
Final error: 0xe000fed1 - A failure occurred querying the Writer status.
Final error category: Resource Errors

For additional information regarding this error refer to link V-79-57344-65233

 

If I am running the command (at the exchange servers that is failing): VSSADMIN LIST WRITERS

 

I am get following error:
 
Writer name: 'Microsoft Exchange Writer'
  Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
  Writer Instance Id: {0bed4cc6-1c89-4051-bb82-bbc1186a9199}
  State: [7] Failed
  Last error: Retryable error 

 

I have read about that error massages and it is mostly resolved when doing a restart of the server.

I have then restarted the server and running a backup again and then the backup is running ok.

But when I am trying to run a second backup without restarting the server I get the same error and it is the same problem with the Exchange Writer.

 

How to permanently solve it? It probably many Symantec backupexe 12 customers that have the same issue!

 

Regards

Jonas

3 REPLIES 3

Vijay_S_Mishra
Level 6
Employee Certified
This is an Windows issue where your exchange writers are not functioning properly and failing repearedly.
You can try applying SP 1 for Exchange 2007 or check with microsoft for this.
 
Thanks,
 

johnez
Level 2

At one of the Exchange 2007 servers that have problem is already exchange SP1

I have posted the question more detailed on Microsoft TechNet

forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3150986&SiteID=17&mode=1

Ubuntop
Level 2
Johnez,

I had the same issue, both with SP1 and without.  A Symantec employee posted a fix on here somewhere and of course blamed microsoft for it.

The gist of the solution was to restart the information store on the Exchange server.  Sounds simple enough, but it worked for both of my servers.  The GRT backups worked fine after that.

U