1. Starting TSM as a service

Solaris 10 introduces a service management system, which can be used to run the scheduled backups with the TSM client. Usually administration of services on a Solaris 10 system requires root privileges. Please note that Solaris 9 will use the init method described in the Linux/Unix documentation.

During the installation of the TSM software you may have been given the option to install the scheduler. If you answered yes to this prompt then you can skip to: 1.3. Checking the CAD has a schedule

1.1. Installing the Scheduler Manually

In the TSM client installation directory, /opt/tivoli/tsm/client/ba/bin, there are scripts named HFSsched-install.sh and HFSsched-remove.sh. These are to install/uninstall TSM as a service. Issue the command:

 $ /opt/tivoli/tsm/client/ba/bin/HFSsched-install.sh

as the root user, to install and start the service. To check that it has installed correctly and is online , do:

 $ svcs -p dsmcad

In order to start the service, as root, issue the following command:

$ svcadm enable dsmcad

1.2. Log files

The CAD and TSM scheduler write to the following log files in /var/log (unless the variable DSM_LOG is set at run time to specify an alternative location)

  • dsmwebcl.log - the logfile of the CAD output.
  • dsmsched.log - the log of the all scheduled backups. This file lists the details of each file processed in the most recent scheduled backups, the summary results of the most recent scheduled backups and the time of the next scheduled backup.
  • dsmerror.log - lists any errors encountered in any manual or scheduled backup.

1.3. Checking the CAD has a schedule

You can check that the CAD is managing the scheduler by examining the latest entry in the /var/log/dsmwebcl.log file. It should look similar to below.

24-05-2007 10:18:09 (dsmcad) IBM Tivoli Storage Manager
24-05-2007 10:18:09 (dsmcad) Client Acceptor - Built Nov 28 2006 09:17:34
24-05-2007 10:18:09 (dsmcad) Version 5, Release 4, Level 0.0
24-05-2007 10:18:09 (dsmcad) Dsmcad is working in    Schedule   mode.
24-05-2007 10:18:09 (dsmcad) Command will be executed
in 1 minute.           
24-05-2007 10:18:09 (dsmcad) Time remaining until execution:
Executing scheduled command now.
24-05-2007 10:19:10 (dsmcad) Next operation scheduled:
24-05-2007 10:19:10 (dsmcad) ------------------------------------------------------------
24-05-2007 10:19:10 (dsmcad) Schedule Name:         WEEKLY_OUCS
24-05-2007 10:19:10 (dsmcad) Action:                Incremental
24-05-2007 10:19:10 (dsmcad) Objects:
24-05-2007 10:19:10 (dsmcad) Options:
24-05-2007 10:19:10 (dsmcad) Server Window Start:   18:00:00 on 29-05-2007
24-05-2007 10:19:10 (dsmcad) ------------------------------------------------------------
24-05-2007 10:19:10 (dsmcad) Command will be executed
in 8 hours             
 and 30 minutes.       
24-05-2007 10:19:10 (dsmcad) Time remaining until execution:

Note that there is a Schedule Name - usually starting WEEKLY_ or WEEKDAILY_ followed by a shortened department or college name.

Checking in /var/log/dsmsched.log the output will look similar to below.

24-05-2007 10:19:09 Next operation scheduled:
24-05-2007 10:19:09 ------------------------------------------------------------
24-05-2007 10:19:09 Schedule Name:         WEEKLY_OUCS
24-05-2007 10:19:09 Action:                Incremental
24-05-2007 10:19:09 Objects:
24-05-2007 10:19:09 Options:
24-05-2007 10:19:09 Server Window Start:   18:00:00 on 29-05-2007
24-05-2007 10:19:09 ------------------------------------------------------------
24-05-2007 10:19:09 Scheduler has been stopped.

Note that the last line 'Scheduler has been stopped' is normal and refers to the TSM scheduler being managed (stopped and started) by the CAD.

Note that if the next schedule window is more than 24 hours away the CAD process will count down for 24 hours and then re-launch the TSM Scheduler to query the TSM server for its next schedule. You can query the schedule window from the command line as below:

dsmc query schedule

Up: Contents Next: 2. Checking the Scheduled Backup has worked

Sections in this document: