Installation and User's Guide

daemon-managed scheduling this is not necessary because the scheduler isrestarted by the client acceptor daemon for each backup.Manage multiple schedule requirements on one systemIn certain situations it is preferable to have more than one scheduled activity foreach client system.Normally, you can do this by associating a node with more than one scheduledefinition. This is the standard method of running multiple schedules on onesystem.You must ensure that the schedule windows for each schedule do not overlap. Asingle client scheduler process is not capable of executing multiple scheduledactions simultaneously, so if there is overlap, the second schedule to start is missedif the first schedule does not complete before the end of the startup window of thesecond schedule.Suppose that most of the drives on your client system must be backed up daily,and that one drive containing critical data must be backed up hourly. In this case,you would need to define two schedules to handle this requirement. To avoidconflict between the hourly and daily backup schedule, the starttime of eachschedule needs to be varied.In certain cases, it is necessary to run more than one scheduler process on asystem. Multiple processes require a separate options file for each process andmust contain the following information:v Define a unique node name for each processv Specify unique schedule and error logs for each processvWhen running in prompted mode, you must use the tcpclientport option tospecify a unique port for each process.Note: When the scheduler runs as a service, processing options specified in theWindows registry override the same options specified in the client options file.The advantages of using multiple schedule processes:v You can run more than one scheduled backup at the same time.v You can specify different backup criteria for each schedule started, with theTivoli Storage Manager client option file or Tivoli Storage Manager serveroverride options.The disadvantages of using multiple schedule processes:v A unique file space for each node name on the Tivoli Storage Manager server iscreated.v When restoring the data, you must use the same node name associated with thebackup.You must create a separate service for each schedule process. If you are using theclient acceptor daemon to manage the scheduler, a client acceptor daemon serviceand schedule service are required for each schedule. The following is an exampleof setting up two schedule processes to be managed by the client acceptor daemon:dsmcutil inst /name:"TSM Client Scheduler1" /optfile:"c:\tsm\dsm.opt1"/node:tsmcli_sched1 /password:secret /autostart:no /startnow:nodsmcutil inst CAD /name:"TSM Client Acceptor1" /optfile:"c:\tsm\dsm.opt1"Chapter 7. Tivoli Storage Manager scheduler overview 231