We're on a Win 2003 server w/ Backup Exec 12.5 rev 2213 and we get the below errors either to tape or USB HD:
Error to USB: e000e020 - The job was scheduled to run, but the availability window closed before the job could start. There may not have been any destination devices available during the window, or the job may have been submitted to run when the window was closed.
Final error: 0xe0008821 - Job was recovered as a result of Backup Exec RPC service starting. No user action is required.
Final error category: Job Errors
Backup- D: V-79-57344-3850 - The media operation was terminated by the user.
Storage device "My Book Duo Backup Drive" reported an error on a request to report current media location.
Error reported:
0x800706ba (2147944122)
V-79-57344-34036 - An unknown error has occurred.
V-79-57344-34108 - An unexpected error occurred when cleaning up snapshot volumes. Confirm that all snapped volumes are correctly resynchronized with the original volumes.
Job completion status: Canceled by service shutdown
I saw this VolSnap thread, but I did't know what to put for "the size that you want for the shadow copy storage area". I also saw this Backup often fails with error "V-79-57344-34108 thread, and here are the results of vssadmin list writers
Waiting for responses.
These may be delayed if a shadow copy is being prepared.
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {482ca8ac-9960-4f6b-91f4-d699938cf3d5}
State: [1] Stable
Last error: No error
Writer name: 'FSRM Writer'
Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
Writer Instance Id: {3af75b45-1900-4a6b-a49b-adcfa42da12a}
State: [1] Stable
Last error: No error
Writer name: 'FRS Writer'
Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
Writer Instance Id: {2e32e77a-5de8-4d64-b92a-6a66234d4304}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {128b0f01-69fd-4306-95d5-176e11d5876c}
State: [1] Stable
Last error: No error
Writer name: 'Dhcp Jet Writer'
Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
Writer Instance Id: {efba714d-8c3b-4144-8eac-9d69bf2cea02}
State: [1] Stable
Last error: No error
Writer name: 'WINS Jet Writer'
Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741}
Writer Instance Id: {a6925102-85ed-4087-a50f-7b2710cce834}
State: [1] Stable
Last error: No error
Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
Writer Instance Id: {4dedf214-9b91-485d-8ad8-bbfcfc4795ce}
State: [1] Stable
Last error: No error
Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {a8f8baf6-8a8b-4b61-acaf-3e9f461ca19f}
State: [1] Stable
Last error: No error
Writer name: 'Event Log Writer'
Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
Writer Instance Id: {46ecaaad-4655-47b2-89e4-0b625710a674}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {ba5c5c72-a8ba-428e-82e0-7e64f9f21fef}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {cd764b76-1082-408e-9c9e-f1259e60e7f8}
State: [1] Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {84bbdc78-3180-4b5a-b53d-9afdf4fd4101}
State: [1] Stable
Last error: No error
There is also this warning filling up the Event Application log/viewer:
Error reading log event record. Handle specified is 649384. Return code from ReadEventLog is 87.