Comparison between client acceptor-managed services and traditional scheduler services

You can use either the client acceptor service or the traditional scheduler service to manage the Tivoli® Storage Manager scheduler. A comparison of these methods is provided.

The following table shows the differences between the client acceptor-managed services and the default traditional scheduler services methods.

Table 1. Client acceptor-managed services versus traditional scheduler services
Client acceptor-managed services	Tivoli Storage Manager traditional scheduler services
Defined by using the `managedservices schedule` option and started with client acceptor services. The client acceptor daemon is started with the dsmcad command The client acceptor service is started as a Windows service	Started with command dsmc sched command.
The client acceptor service starts and stops the scheduler process as needed for each scheduled action.	Remains active, even after scheduled backup is complete.
Requires fewer system resources when idle.	Requires higher use of system resources when idle.
Tivoli Storage Manager client options and Tivoli Storage Manager server override options are refreshed each time the client acceptor services start a scheduled backup.	Tivoli Storage Manager client options and Tivoli Storage Manager server override options are only processed after dsmc sched is started.
Cannot be used with `SESSIONINITiation=SERVEROnly` backups.	You must restart the scheduler process for updated Tivoli Storage Manager options to take effect. Important: If you run the client scheduler on the command line, the scheduler does not run as a background service. Tip: Restart the traditional scheduler periodically to free system resources previously used by system calls.