Question : VSS Writer Failed

Hello,
i know in my error message I have the link to the tech article that tells what to do if a backup job fails but have tried that and other things with little luck.
Every week at least once a week my backup job on Exchange 2007 fails with the following error...
Final error: 0xe0008488 - Access is denied. &
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).
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: Stable (1).
-However if I run a VSS check writers command on my exchange server I have all of them being healthy with no issues.  Any thoughts?  Has anyone else had this issue and what did you do other then restarting Exchange everytime this happens???
Please Advise and thanks a bunch!!!

Answer : VSS Writer Failed

There was a recent hotfix that Symantec release...  it was mainly released to fix a bug in 12.5 where backing up Exchange 2 Tape, would results in on 32 cataloged mailboxes for GRT when you try to restore.  The hotfix seems to have fixed this VSS Writer error for us.  We also added 4 extra gig of ram to each cluster node upping it to 8 gig, as well as have patched exchange to rollup 6.  Lastly we have a scheduled task that runs every Mon, Wed, Fri, which restarts the backup agent service on both exchange nodes.  This is a seperate issue that we learned about with 12.5 where after about a week of backups on exchange the agent would not be releasing it's memory load and the beservice.exe (not sure of exact process name) would be using over 1+ gig of memory.  This was obviously causing performance issues on the exchange side.

Hope this helps anyone that sees this!
Random Solutions  
 
programming4us programming4us