IBM Tivoli Storage Manager, Version 7.1

Set the client scheduler process to run as a background task and start automatically at startup

You can configure the Tivoli® Storage Manager client scheduler to run as a background system task which starts automatically when your system is started.

This is true whether you use the client acceptor daemon (CAD) to manage the scheduler or whether you use the traditional method to start the scheduler client scheduler.

AIX operating systems HP-UX operating systems Linux operating systems Oracle Solaris operating systems Mac OS X operating systems When you are running a client acceptor daemon-managed schedule, only the client acceptor daemon process should be set to start automatically at startup time; not the scheduler process. For the traditional method, the scheduler process should be set up to start automatically at startup time.

AIX operating systems HP-UX operating systems Linux operating systems Oracle Solaris operating systems Mac OS X operating systems You can configure the client acceptor daemon to run as a background system task which starts automatically when your system is started. To configure the client acceptor daemon to manage scheduled backups, you use the managedservices option to specify whether the CAD manages only the scheduler, only the web client, or both the scheduler and web client. The method for setting up the client acceptor daemon as a system task varies for each platform.

For the scheduler to start unattended, you must enable the client to store its password by setting the passwordaccess option to generate, and store the password by running a simple Tivoli Storage Manager client command such as dsmc query session. Note that for testing purposes, you can always start the scheduler in the foreground by running dsmc sched from a command prompt (without a managedservices stanza set).

AIX operating systems HP-UX operating systems Linux operating systems Oracle Solaris operating systems Mac OS X operating systems To start the scheduler automatically at startup time, use either the CAD managed method or the traditional method.

AIX operating systems HP-UX operating systems Linux operating systems Oracle Solaris operating systems Mac OS X operating systems
Client acceptor daemon managed method
  1. In your dsm.sys file, set the managedservices option to schedule or schedule webclient.
  2. Start the client acceptor daemon.
    1. AIX operating systems HP-UX operating systems Oracle Solaris operating systems
      On AIX®, HP-UX, and Solaris clients, add the following entry into the system startup file (/etc/inittab for most platforms):
      tsm::once:/usr/bin/dsmcad > /dev/null 2>&1 # TSM Client 
      Acceptor Daemon
    2. Linux operating systems
      On Linux clients, the installation program creates a startup script for the client acceptor daemon (dsmcad) in /etc/init.d. The client acceptor daemon (dsmcad) must be started before it can manage scheduler tasks, or manage the web client. As root, use the following command to start, stop, or restart the daemon, or check its status:
      Read syntax diagramSkip visual syntax diagram
      >>-service dsmcad--+-start---+---------------------------------><
                         +-stop----+   
                         +-restart-+   
                         '-status--'   
      
      
      To enable the Client Acceptor Daemon to start automatically after a system restart, add the service as follows, at a shell prompt:
      # chkconfig --add dsmcad
    3. Mac OS X operating systems On Mac OS X, the Tivoli Storage Manager client acceptor daemon must be installed as a Startup Item. A system administrator must use the Tivoli Storage Manager Tools for Administrators to install and start the client acceptor daemon. To start, stop, or restart the daemon, use the following command:
      Read syntax diagramSkip visual syntax diagram
      >>-sudo /sbin/SystemStarter--+-start---+--dsmcad---------------><
                                   +-stop----+           
                                   '-restart-'           
      
      
  3. In your dsm.sys file, set the passwordaccess option to generate.
  4. Run a command like dsmc query sess to store the node password.
AIX operating systems HP-UX operating systems Linux operating systems Oracle Solaris operating systems Mac OS X operating systems Traditional method:
  1. Set the managedservices option.
    • AIX operating systems HP-UX operating systems Linux operating systems Oracle Solaris operating systems On AIX, HP-UX, Linux, and Solaris clients, either remove the option entirely (it defaults to webclient) or set it to webclient.
    • Mac OS X operating systems On Mac OS X clients, set the managedservices option to either webclient or none. Do not set the option to schedule.
  2. On AIX, HP-UX, Linux, and Solaris, add the following entry into the system startup file, for example, /etc/inittab, where it is supported:
    tsmsched::once:/usr/bin/dsmc sched > /dev/null 2>&1 # TSM scheduler
  3. In your dsm.sys file, set the passwordaccess option to generate.
  4. Run a command like dsmc query sess to store the node password.
  5. To start the client scheduler on your client node and connect to the server schedule, enter the following command:
       dsmc schedule
    If the current directory is not in your PATH environment variable, enter the following command:
       ./dsmc schedule 

    When you start the client scheduler, it runs continuously until you close the window, end the process, or log off your system.

    To run the schedule command in the background and to keep the client scheduler running, even if you log off your system, enter the following command:
       nohup dsmc schedule 2> /dev/null &

Windows operating systems On Windows platforms, the scheduler and the client acceptor daemon run as services. You can create and manage these services by using either the setup wizard or the Tivoli Storage Manager Client Service Configuration Utility, dsmcutil.exe.

Windows operating systems

Windows operating systems The Tivoli Storage Manager client scheduler can be managed by the client acceptor daemon. When setting up Tivoli Storage Manager scheduler services to run with client acceptor daemon management, two services must be created: the scheduler service and the client acceptor daemon service. When you install the client acceptor daemon service with dsmcutil.exe, use the /cadschedname: parameter to identify which Tivoli Storage Manager scheduler service the client acceptor daemon manages. If you use the setup wizard to install the scheduler, you can select the Use the CAD to manage the scheduler check box, which automatically creates both services and associates them.

Windows operating systems Using the Client Service Configuration Utility, you can use either of the following methods:

Windows operating systems
Client acceptor daemon-managed method
  1. In your client options file (dsm.opt), either set the managedservices option to schedule or schedule webclient.
  2. In your client options file (dsm.opt), set the passwordaccess option to generate.
  3. Create the scheduler service:
    dsmcutil inst /name:"TSM Client Scheduler" /node:tsmclient1
    /password:secret /autostart:no /startnow:no
  4. Create the client acceptor daemon and associate scheduler service with the client acceptor daemon:
    dsmcutil inst CAD /name:"TSM Client Acceptor" /cadschedname:
    "TSM Client Scheduler" /node:tsmclient1 /password:secret /autostart:yes 
  5. Manually start the client acceptor daemon service:
    net start "TSM Client Acceptor"
Traditional method
  1. In your client options file (dsm.opt), either remove the managedservices entirely (it defaults to webclient) or set it to webclient.
  2. In your client options file (dsm.opt), set the passwordaccess option to generate.
  3. Create the scheduler service:
    dsmcutil inst /name:"TSM Client Scheduler" /node:tsmclient1
    /password:secret /autostart:yes

Windows operating systems To increase the reliability of the Tivoli Storage Manager client scheduler service on Windows, you should set the services to automatically recover from a failure, as follows:

Windows operating systems

Windows operating systems If you are using the client acceptor daemon to manage the scheduler, you must set the recovery properties for the TSM Client Acceptor service, but leave the recovery settings for the TSM Client Scheduler as Take No Action for the first, second, and subsequent failures. The same recovery settings can also be defined to increase the reliability of the TSM Journal Service.



Feedback