VSS Writer Fails backing up Exchange 2007 SP1 Cluster
Since applying Exchange 2007 SP1, about 2/3 of our Exchange IS (w/ GRT) backups say they complete successfully, but only backup one of our two stores. Each one displays the following error:
Writer Name: Microsoft Exchange Writer, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Failed during backup complete operation (12).
I just tried the job right now, got that error, and checked the Exchange VSS writers on both nodes of our cluster. Both show Stable and No Error. Prior to applying SP1, we had no error and the same job ran successfully every night for about four months. I did a cursory search of these forums and some suggested updates to the VSS writers ... specifically, KB940349, which I applied but no difference. The Exchange servers are Windows Server 2003 x64, with SP2 and all critical updates applied.
In the event logs on the cluster, I see two warnings and two errors:
First a warning on the active member, ESE BACKUP, 'surrogate backup' stopped with error 0xFFFFFFFF.
Next, an error on the active member, ESE, the backup has been stopped because it was halted by the client or the connection failed.
Next, a warning on the passive member, MSExchangeRepl, the VSS Writer failed.
Last, an error on the passive member, MSExchangeRepl, VSS Writer failed with code FFFFFFFC when processing the backup completion event. (C = 12 = the State in the BE error??)
On the backup jobs that do backup both stores, there are no errors or warnings in the event viewer.
This problem was brought on by the SP1 upgrade obviously ... is this a VSS problem or a cluster problem or what?
Comments
Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
Writer Instance Id: {a90f8a48-3dab-479b-9e77-ea328e79220a}
State: [10] Failed
Last error: No error
I fixed this. My backups ran fine without GRT turned on but crapped out with VSS errors when I had it enabled.
Turn off AOFO for your exchange backups. Works like a champ now for me.
I'm also experiencing this issue with a Windows 2008 Exchange 2007 SP1 running with LCR in VMWare. We started seeing this issue once we upgraded to BE v12.5, didn't have this issue with v12.
The workaround we found is to select to backup the Active database instead of the Passive one in the AOFO options of BackupExec. However, I'd like to switch back to the Passive if this ever gets resolved.
I know this is really old,
I know this is really old, but perhaps someone can suggest what might have fixed it for them?
Same sort of scenario, Exchange 2007 SP1 on Win 2003 server with SP2 with BE 12 (sp3), getting much in the same errors as the original poster and just wondering what anyone was able to do to resolve this?
As we speak I am running a backup of the active databse to see if that resolves the issue (after rebooting exchange due to failed writer status) but if that doesn't work then I am back to square 1.
Thanks in advance!
Would you like to reply?
Login or Register to post your comment.