Veritas BackupExec 9.1 (Errors)

what is E drive ? standard drive ?

it looks like some options need to be disabled on the backup exec.

Yes, the E: drive is a standard RAID 5 array.  What options do you recommend disabling?  The "E" drive is important as it stores users home directories, as well our shared drive.

what is the error on the event viewer ?

Stop the shadow service and try using veritas again to see if it fails.

Maybe this could help:

http://seer.support.veritas.com/docs/265927.htm

I'll be trying the aforementioned suggestions this evening and will advise tommorrow.  Thank you gentleman...I'll accept whicheve answer resolves my problem.

Volume Shadow Copy service is Stopped.  Start it.

Hi Duckey:

Your comment was indicated in my link at the bottom:  

"Hence, while configuring a backup job to back up a Windows 2003 machine with selections made from the Shadow Copy Components, it should be ensured that the Microsoft Software Shadow Copy Provider Service and the Volume Shadow Copy Service are running."

All:

None of the suggestions have worked, however when I query my writers status I see the following writers all except one are in state FAILED.  I should also note this problem started once I upgrade from W2K Server to W3K Server Standard.  Any suggestions?

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {87e9ad5c-2a72-4915-bd82-34241262500c}
   State: [7] Failed
   Last error: No error

Writer name: 'MSDEWriter'
   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
   Writer Instance Id: {d371e84b-3a95-4045-932d-f5df86a69274}
   State: [1] Stable
   Last error: No error

Writer name: 'WINS Jet Writer'
   Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741}
   Writer Instance Id: {46a6aff5-1398-411b-9728-c6162a9ed258}
   State: [7] Failed
   Last error: No error

Writer name: 'Removable Storage Manager'
   Writer Id: {5d3c3e01-0297-445b-aa81-a48d7151e235}
   Writer Instance Id: {62116cd8-cee2-48f5-a12b-f863861ae880}
   State: [7] Failed
   Last error: No error

Writer name: 'TermServLicensing'
   Writer Id: {5382579c-98df-47a7-ac6c-98a6d7106e09}
   Writer Instance Id: {670df1b1-af67-45c5-b0f1-95734f86a678}
   State: [7] Failed
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {5ec624cf-787f-4048-9b00-d44586f2bc57}
   State: [7] Failed
   Last error: No error

Writer name: 'Dhcp Jet Writer'
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {58ba63f4-a6b9-4448-b830-ca1434851041}
   State: [7] Failed
   Last error: No error

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {cb7c4cdc-c009-4c96-a60b-4394d9081ecc}
   State: [7] Failed
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {664858d0-eded-4eb5-b6af-fbb1834c1084}
   State: [7] Failed
   Last error: No error

Writer name: 'FRS Writer'
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {e82eaa92-5e1b-4eea-a265-4bf9115f2760}
   State: [7] Failed
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {96bf1b5b-5d19-454c-9cd1-f1e164055959}
   State: [7] Failed
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {214eda09-ef58-4c7c-92b9-85cfe2b06834}
   State: [7] Failed
   Last error: No error

Writer name: 'Event Log Writer'
   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
   Writer Instance Id: {80a567e1-8b00-44c0-b656-469396151d4d}
   State: [7] Failed
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {edb58757-518e-4000-8f47-13b1b485bee8}
   State: [1] Stable
   Last error: No error

FYI.  Apparently good ol' microsoft has a known issue with VSS in W3K Standard.  They have a patch they provide when you contact their support group.  The patch isn't publicly available.  This resolved my issue.

Please PAQ this question.  Thank you.