2. Checking the Scheduled Backup has worked

Output from the Scheduler process is appended to the end of the dsmsched.log file and any errors are written to the dsmerror.log file. It is important to regularly examine the schedule log for details of the latest scheduled backups. The TSM Scheduler will have written summary information of the last scheduled backup similar to below 

02-12-2009 18:36:28 Normal File-->               539 /var/log/exim4/mainlog.9.gz [Sent]
02-12-2009 18:36:28 Normal File-->                 9 /var/spool/anacron/cron.daily [Sent]
02-12-2009 18:36:28 ANS1802E Incremental backup of '/' finished with 3 failure
        
02-12-2009 18:36:28 --- SCHEDULEREC STATUS BEGIN
02-12-2009 18:36:28 Total number of objects inspected:  184,395
02-12-2009 18:36:28 Total number of objects backed up:      995
02-12-2009 18:36:28 Total number of objects updated:         26
02-12-2009 18:36:28 Total number of objects rebound:          0
02-12-2009 18:36:28 Total number of objects deleted:          0
02-12-2009 18:36:28 Total number of objects expired:        782
02-12-2009 18:36:28 Total number of objects failed:           3
02-12-2009 18:36:28 Total number of bytes transferred:   498.21 MB
02-12-2009 18:36:28 Data transfer time:                   39.90 sec
02-12-2009 18:36:28 Network data transfer rate:        12,786.00 KB/sec
02-12-2009 18:36:28 Aggregate data transfer rate:      3,470.37 KB/sec
02-12-2009 18:36:28 Objects compressed by:                    0%
02-12-2009 18:36:28 Elapsed processing time:           00:02:27
02-12-2009 18:36:28 --- SCHEDULEREC STATUS END
02-12-2009 18:36:28 --- SCHEDULEREC OBJECT END WEEKLY_18_30 02-12-2009 18:30:00
02-12-2009 18:36:28 Scheduled event 'WEEKLY_18_30' completed successfully.
02-12-2009 18:36:28 Sending results for scheduled event 'WEEKLY_18_30'.
02-12-2009 18:36:28 Results sent to server for scheduled event 'WEEKLY_18_30'.
          
02-12-2009 18:36:28 ANS1483I Schedule log pruning started.
02-12-2009 18:36:28 ANS1484I Schedule log pruning finished successfully.
02-12-2009 18:36:28 TSM Backup-Archive Client Version 6, Release 1, Level 0.2
02-12-2009 18:36:28 Querying server for next scheduled event.

The first thing is to look for whether the schedule completed successfully or not. A 'completed successfully' message indicates that most, if not all, of your files have been successfully backed.

Next, it is important to determine if any files have failed to backup. If the 'Total number of objects 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 this case, the choice is either to close the program before the backup, or exclude the file from the backup process. Examples of how to do this can be found in our page on how to exclude files and folders from backup.

Note that files failing to backup because they are held open by other processes do not preclude a backup schedule completing successfully.

Other failures and errors will be accompanied by an error message and a corresponding entry in the dsmerror.log file.

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.sys file. By default this is set to 30 days. See the entry in the TSM client online Help for possible values for this option.

Up: Contents Previous: 1. Starting the TSM Scheduler Next: 3. Troubleshooting