Previous Topic: Notifying Operator of Failed Backup OperationsNext Topic: Rerunning Backup of Skipped Files


Investigating the Cause of Failed Backup Operation

The following example shows you how to discover the reason for backup failures by locating the lines in the log that have triggered the severity condition.

To locate the lines in the log, follow these steps:

  1. Open the TSM Nodes table.
  2. Select a node with a Fatal severity level. It is easier to make the selection if you have assigned colors to severity levels.
  3. To examine the entries in the log file that triggered this level, click the Result File button.
  4. When the Result file appears in the editor, the cursor points to the string pattern that triggered the severity. Below the string pattern, the editor lists all the log lines that contain the pattern.
  5. Address the fault situation, then close the editor.
  6. To reset the Severity level of the TSM node, click the Reset Severity button. This sets the severity level of the node to Harmless.
  7. Repeat Steps 2-6 for all TSM nodes that show a severity other than Harmless, until you complete investigating the causes for backup failures on all TSM nodes.