What errors generate a "Failed" status in EVENTS

[F784927]

Is there any documentation available on what errors generate a "Failed" Status on a scheduled backup? It appears that: "ANS1228E Sending of object '\\pfgdsmedm011\c$\WINNT\Profiles\dmadmin.000\NTUSER.DAT' failed OR "ANS4987E Error processing '\\pfgdsmedm011\c$\WINNT\Profiles\dmadmin.000 \NTUSER.DAT': the object is in use by another process" DOES NOT, but "01/27/2004 22:03:08 ANS4023E Error processing '\\pfgdsmedmdev1\c$\se5.1rr': file input/output error" DOES.



I'd like to know what all makes it a failed backup because I might want to wake someone up in the night on some failures with a page but others just email them to look at the next day?



any ideas?



Thanks

 

[Jeroen]

See the client-manual for Windows (5.1 and higher).

http://publib.boulder.ibm.com/tividd/td/TSMC/GC32-0788-01/en_US/HTML/ans60000tfrm.htm



Code Explanation

0 All operations completed successfully.



4 The operation completed successfully, but some files were not processed. There were no other errors or warnings. This return code is very common. Files are not processed for various reasons. The most common reasons are:

* The file is in an exclude list..

* The file was in use by another application and could not be accessed by the client

* The file changed during the operation to an extent prohibited by the copy serialization attribute. See "Copy Serialization".



8 The operation completed with at least one warning message. For scheduled events, the status will be "Completed". Review dsmerror.log (and dsmsched.log for scheduled events) to determine what warning messages were issued and to assess their impact on the operation.



12 The operation completed with at least one error message (except for error messages for skipped files). For scheduled events, the status will be "Failed". Review dsmerror.log (and dsmsched.log for scheduled events) to determine what error messages were issued and to assess their impact on the operation. As a general rule, this return code means that the error was severe enough to prevent the successful completion of the operation. For example, an error that prevents an entire drive from being processed yields return code 12. When a file is not found the operation yields return code 12.