Air Cleaner User Manual

Problem Determination
Understanding basic SysBack and TSM problem determination tools may help you
resolve minor problems without the need to contact support. In those situations
where you would like to contact support for assistance, understanding the tools
that support may ask you to use may be helpful as well.
There are 3 primary items that you should monitor or review periodically to
ensure that all of your backup processes are functioning properly. They are:
v The SysBack command output
v The SysBack Activity Log
v The SysBack error log for the TSM API
The SysBack Command Output
The most effective way to ensure that your backup operations are completing
without error is to save the output from the backup operation. Sometimes, a
backup completes with a status of success but also had warning messages. In order
to determine what exactly caused the warning, you will need to look at the output
from the command. There have been scenarios where an overall backup process
completed successfully, but due to an unforeseen operating system issue, much of
the data was not actually backed up.
In order to capture the output of the SysBack backup operations, you must redirect
standard output and standard error to a file.
This may be achieved by issuing your command in a manner like this:
/usr/sbin/sysback -f tsm0 datavg > /tmp/backup.log 2>&1
If you would like to monitor the backup process on your screen and save the
output to a file at the same time, you could issue a command like this:
/usr/sbin/sysback -f tsm0 datavg 2>&1 | tee /tmp/backup.log
There are several different methods for capturing the standard output (stdout) and
standard error (stderr) from a command. There are also several ways to rotate your
backup logs or to dynamically created the log name. Simply choose the method
that is appropriate to your environment.
The SysBack Activity Log
SysBack provides a basic Activity Log that indicates the start date and time of all
backup, restore and verify operations. It also includes the command issued, and if
the command was successful, failed, and / or had warnings.
For more information regarding the SysBack Activity Log, please refer to:
Chapter 19, “Activity Logging”, on page 19-1.
SysBack Error Log for the TSM API
The TSM API error log specific to the SysBack initiated communications is located
at /usr/lpp/sysback/sbtsmerror.log. You should periodically review this file for
issues related to TSM server communications.
Note: You can override this location by setting the DSMI_LOG environment variable
in your .profile or.kshrc file.
15-26 IBM Tivoli Storage Manager for System Backup and Recovery: Installation and User’s Guide