12.07.2015 Views

IBM Tivoli Storage Manager for UNIX and Linux Backup-Archive ...

IBM Tivoli Storage Manager for UNIX and Linux Backup-Archive ...

IBM Tivoli Storage Manager for UNIX and Linux Backup-Archive ...

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

The schedule log file typically resides in the same directory as the <strong>Tivoli</strong> <strong>Storage</strong><strong>Manager</strong> client error log (dsmerror.log), in a file named dsmsched.log. The locationof the log file can be specified using the schedlogname option, so you might needto refer to the options file to see if the schedlogname option was used to relocatethe log file. When you locate the schedule log, it is easy to search through the fileto find the time period corresponding the start date <strong>and</strong> time of the scheduledevent. Here are some tips on what to look <strong>for</strong>:vvvIf you are investigating a missed event, check the details of the previous event,including the time at which the previous event completed.If you are investigating a failed event, look <strong>for</strong> error messages which explain thefailure, such as an exceeded <strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong> server session limit.If an explanation remains unclear, check the client error log file (usually nameddsmerror.log.)Note: On Mac OS X, the default location <strong>for</strong> the scheduler log file is/Library/Logs/tivoli/tsm. The Console application can be used to view the log.Underst<strong>and</strong>ing the scheduler logThe scheduler log file provides in<strong>for</strong>mation about which schedule runs next <strong>and</strong>which files are processed.The schedule log continues to grow in size unless you prune it using theschedlogretention option or specify a maximum size using the schedlogmax option.When the scheduler queries the server <strong>for</strong> the next schedule, it sends the schedulein<strong>for</strong>mation to the log file. The following in<strong>for</strong>mation is logged:Table 46. Schedule log in<strong>for</strong>mationCategoryDescriptionSchedule nameSpecifies the name the administrator assigns to the schedule.ActionSpecifies the type of task to per<strong>for</strong>m on the files listed in theObjects field:v Incremental. Incrementally backs up the files.v Selective. Backs up the files.v <strong>Archive</strong>. <strong>Archive</strong>s the files.v Restore. Restores the files.v Retrieve. Retrieves the files.v Comm<strong>and</strong>. Executes a client operating system comm<strong>and</strong>described in the Objects field.v Macro. Executes a macro whose file name is described in theObjects field.ObjectsNames the volumes or files to process. If the action is abackup, archive, retrieve, or restore operation, the objects arefile spaces, directories, or logical volumes. If this field is empty<strong>for</strong> an incremental backup, then the default is used. If theaction is to run a comm<strong>and</strong> or macro, the object is the name ofthe comm<strong>and</strong> or macro to run.OptionsOverrides options that you set <strong>for</strong> scheduling in yourPreferences file.Server window start Specifies the date <strong>and</strong> time when the next schedule will run. Ifthe server uses r<strong>and</strong>omization <strong>for</strong> schedules, the schedule thenruns after the specified time.Chapter 7. Using the <strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong> central scheduler 225

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!