4. Checking the Scheduled Backups
The TSM Scheduler writes its output to the end of the
dsmsched.log file and any errors in the
dsmerror.log file. It is important to regularly examine the schedule log for details of the
latest scheduled backups. To do this open the
dsmsched.log file and scroll to the end of the
file. The TSM Scheduler will have written summary information of the last scheduled backup similar to below
It is important to determine if any files have failed to backup. If the number of objects listed as failed is
greater than zero then scroll up the file for the next occurrence of the word 'fail' to determine which file(s)
this affects. The most common reason for a file failing to be backed up is that it is held open (locked) by another
program. In some cases this is unavoidable: the file
should be ignored if it fails and should not be excluded from the backup. In other cases, the choice is
either to close the program before the backup, or exclude the file from the
backup process by adding it to the
Exclude entries in the
dsm.opt options file.
Other failures and errors will be accompanied by an error message and a corresponding entry in the
dsmerror.log file. Further help with any errors may be found using either the TSM Help facility
or the OUCS TSM Help pages.
Note that the schedule log file does not grow endlessly, but is pruned of entries older than the setting of the
SchedlogRetention option in the
dsm.opt options file. By default this
is set to 30 days. See the entry in the client TSM online Help for possible values for this option.