cancel
Showing results for 
Search instead for 
Did you mean: 

Backup Exec 2010 R3 Job fails during Exchange 2007 full backup

timjeens
Level 3

HI All,

My Exchange Full backup keeps failiing with this error:

 

Error category    : Security Errors
Error             : e0001904 - A failure occurred querying the Writer status.  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 snapshot operat
For additional information regarding this error refer to link V-79-57344-6404

The link that it refers to is irrelevant, it mentions events that do not occur.

Can any one help, or at least point me in the right direction.

If you need more info please ask.

Thanks,

-Tim

11 REPLIES 11

Sush---
Level 6
Employee Accredited Certified

On the Exchange server open the command promp and run the following command:

VSSADMIN LIST WRITERS

This will display the status of all the writers on the server which will also include the Exchange writers. Check the status of the Exchange writers (it may be Unstable).

If th status of Exchange writers is Unstable then you will have to reboot the Exchange server and then try the backups.

 

Thanks,

-Sush...

timjeens
Level 3

Hi Sush,

Thanks for the reply, unfortunately I have done that, and they were all No Errors.

V Confusing.

-Tim

timjeens
Level 3

Here is the output from it:

 

C:\WINDOWS>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
 
Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {bda8af14-517d-4a71-b1d3-ecad4d31b504}
   State: [1] Stable
   Last error: No error
 
Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {7bad1c55-c109-4ca3-8bd4-fa140bca36c9}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {09fc7804-b082-4a3f-8573-e38cb92f07b3}
   State: [1] Stable
   Last error: No error
 
Writer name: 'MSDEWriter'
   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
   Writer Instance Id: {56a2f4ae-1b40-4665-b670-f09086850b12}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {881b6c7e-221f-4216-b47f-cf8d662b4d98}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Event Log Writer'
   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
   Writer Instance Id: {19c8b45e-a15c-49df-b34b-da7274806a85}
   State: [1] Stable
   Last error: No error
 
Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {c2fda47f-f581-4122-9253-cdc4787caff3}
   State: [1] Stable
   Last error: No error
 
Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {6df60fca-cd0d-4718-a886-58d6bf73127f}
   State: [1] Stable
   Last error: No error
 
 
and I have previously rebooted and it has still come up with this error.
 
Thanks,
 
-Tim

ZeRoC00L
Level 6
Partner Accredited

Is this export from immediately after the backup has failed ?

If not, run a backup, after failure run the vss list writers command.

CraigV
Moderator
Moderator
Partner    VIP    Accredited

Hi Tim,

 

It doesn't matter if your VSS writers show as failed in the details you provided before or after the backup...if they failed before the backup, it explains the failed backup. If they failed after the backup, they still need to be fixed.

You have 2 options, both of which I'd personally do:

1. Run the VSS Rollup Patch from the MS site and install it. Once done, reboot your server and run: vssadmin list writers again to check they are stable:

http://support.microsoft.com/kb/940349

2. ...if they are, leave it as is. If not, reregister the VSS *.dlls using the Symantec TN below:

http://www.symantec.com/business/support/index?page=content&id=TECH70486

 

Report back with an update.

 

Thanks!

timjeens
Level 3

Hi Craig,

I have previously done step 1, and so obv didn't have an impact.

I can't do Step 2, as that is for 2008 and my exchange is on 2003.  Though there was a link to another MS KB article that had similar fixes (http://support.microsoft.com/kb/940032).

So I have done them and we will see if that makes a difference.

Also fyi, a reboot (of exchange) always manages to fix it, but after a while it then fails again.

Cheers,

-Tim

ZeRoC00L
Level 6
Partner Accredited

Any errors in the eventlog of the Exchange server at the same time as the backup runs ?

CraigV
Moderator
Moderator
Partner    VIP    Accredited

Hi Tim,

 

I've used #2's Symantec TN to successfully reregister the VSS DLLs on a Server 2008 server...you just need to create the batch file, and run it with adminstrator rights...nothing to it. You don't need a server restart and it doesn't interfere with anything. I've done it a number of times over the past couple of months. Exchange doesn't have anything to do with reregistering the *.dlls.

 

Thanks!

timjeens
Level 3

Ah I thought it was supposed to be done on the exchange server.  OK have run it on the backup server.

I take it that this does not permanently fix this issue?

Would you recommend setting it as a scheduled task to run once a week/month?

@ZeRo: There are not any relevant events, apart from the failed job (standard message), on either servers.

Cheers,

-Tim

newsolutionBE
Level 6

Hi

 

Can you please ensure while your exchange backup job is runnin during same time window database maintainence is not scheduled for exchange databases if so please change the schedule

 

Thanks

CraigV
Moderator
Moderator
Partner    VIP    Accredited

Well, you'll run it on the server giving you those VSS issues. So if it is on the Exchange server, run the fix there.

If using Win2K3, the Microsoft TN that is listed points you to a small executable that you download and run. Again, this is nonintrusive and reregisters your *.dlls.

http://support.microsoft.com/kb/940032