Symantec Backup Exec is failing nightly

My backup has failed 3 times this week.  Now the only thing that has changed this week is i moved the scheduled time up 2 hours to 730pm instead of 530pm.  The drive on which exchange is installed is running very low on space less than 2gb.  I am in the process of getting a new server ready for a migration.  I have since moved the schedule back to 530pm because i feel it may be conflicting with other scheduled tasks.

I have attached the log files from SBE as a resource.
Job-Log-BEX-NTSERVER3-04099-xml.mht
Job-Log-BEX-NTSERVER3-04101-xml.mht
Job-Log-BEX-NTSERVER3-04103-xml.mht
telperiongroupAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Senthil KumarConnect With a Mentor Commented:
AOFO Error on the log. You might need to re-register the VSS writer.Check the below link for solution

http://www.symantec.com/connect/forums/be2010r3-aofo-initialization-failure-using-vss-vss-snapshot-failed
0
 
telperiongroupAuthor Commented:
i will implement the two KB articles this weekend but it did run the vssadmin list writers and received no errors with regards to VSS


U:\Administrator>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-lin
(C) Copyright 2001 Microsoft Corp.

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {4b713432-70be-48e0-9cfe-dff6ee584a2b}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {ac8d9f7c-9a05-4437-8b3d-9773c86bb66d}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {622c6217-e0c5-4216-8311-001760c48df9}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {284b5123-1e4e-47c4-aeb3-bbba0ba73bde}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {c6fc78c3-5b01-4d6a-be33-bd9a5f525ee9}
   State: [1] Stable
   Last error: No error

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {727c4418-7229-446b-8ece-0cc619accb2c}
   State: [1] Stable
   Last error: No error

Writer name: 'MSDEWriter'
   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
   Writer Instance Id: {6f65bea9-b1be-4c51-8ec6-f50c33bf10ca}
   State: [1] Stable
   Last error: No error

Writer name: 'Event Log Writer'
   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
   Writer Instance Id: {184e6443-11b9-4fbd-8d84-1aa132c214af}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {7471f7a2-ab63-4af1-92c2-923cb0c181d8}
   State: [1] Stable
   Last error: No error
0
 
telperiongroupAuthor Commented:
so after 4 successful backups, last nights failed again with the following errors.

V-79-57344-65233 - AOFO: Initialization failure on: "\\NTSERVER3\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 timed out (0x800423f2), State: Failed during freeze operation (9).

I did apply the vss update form Microsoft kb940349-v3-x86 last week.

I have attached the latest log file to.

Thanks in advance for any help..
Job-Log-BEX-NTSERVER3-04120-xml.mht
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.