Tivoli Storage Manager for Sun Solaris Administrator's Guide


Managing Event Records

Each scheduled client operation is called an event. All scheduled events, including their status, are tracked by the server. An event record is created in the server database whenever processing of a scheduled command is created or missed.

You can perform the following activities when managing event records:

Task Required Privilege Class
Displaying information about scheduled events Any administrator
Setting the retention period for event records System
Deleting event records System or unrestricted policy

Displaying Information about Scheduled Events

You can display information about scheduled and completed events with the QUERY EVENT command.

To minimize the processing time when querying events:

To help manage schedules for client operations, you can request information about scheduled and completed events. You can request general or exception reporting queries.

Displaying Events that Ended Successfully

You can display information about scheduled events that ended successfully by issuing the QUERY EVENT command. If the administrator specifies a time range that includes the future, TSM displays the future events with a status of future.

Figure 50 shows an example of a general report for client node GOODELL that is displayed after you enter:

query event standard weekly_backup node=goodell
enddate=today+7

Figure 50. General Report of Events

+--------------------------------------------------------------------------------+
|Scheduled Start      Actual Start         Schedule Name Node Name     Status    |
|-------------------- -------------------- ------------- ------------- --------- |
|03/09/1998 06:40:00  03/09/1998 07:38:09  WEEKLY_BACKUP GOODELL       Started   |
|03/16/1998 06:40:00                       WEEKLY_BACKUP GOODELL       Future    |
|                                                                                |
+--------------------------------------------------------------------------------+

Displaying Events that Ended Unsuccessfully

You can display information about scheduled events that ended unsuccessfully by using exception reporting. For example, you can issue the following command to find out which events were missed in the previous 24 hours, for the DAILY_BACKUP schedule in the STANDARD policy domain:

query event standard daily_backup begindate=-1 begintime=now
enddate=today endtime=now exceptionsonly=yes

Figure 51 shows an example of the results of this query. To find out why a schedule was missed or failed, you may need to check the schedule log on the client node itself. For example, a schedule can be missed because the scheduler was not started on the client node.

Figure 51. Exception Report of Events

+--------------------------------------------------------------------------------+
|Scheduled Start      Actual Start         Schedule Name Node Name     Status    |
|-------------------- -------------------- ------------- ------------- --------- |
|03/06/1998 20:30:00                       DAILY_BACKUP  ANDREA        Missed    |
|03/06/1998 20:30:00                       DAILY_BACKUP  EMILY         Missed    |
|                                                                                |
+--------------------------------------------------------------------------------+

Removing Event Records from the Database

You can use the SET EVENTRETENTION command to specify how long TSM retains event records before automatically deleting them from the database. You can can manually delete event records from the database, if database space is required.

If you query the server for events, TSM may display past events even if the event records have been deleted. Such events are displayed with a status of Uncertain indicating that complete information is not available because the event records have been deleted. To determine if event records have been deleted, check the message that is issued after the DELETE EVENT command is processed.

Setting the Event Retention Period

By default, TSM retains event records for 10 days before automatically removing them from the database. The administrator can modify the retention period for event records in the database. To increase the retention period to 15 days, enter:

set eventretention 15 

TSM automatically deletes event records from the database after the specified event retention period has passed and after the startup window for the event has elapsed.

Deleting Event Records

By default, TSM automatically deletes event records from the database. However, you may want to manually delete event records to increase available database space. For example, to delete all event records written prior to 11:59 p.m. on June 30, 1998, enter:

delete event 06/30/1998 23:59


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]