Client-acceptor scheduler services versus the traditional scheduler services

You can configure the Tivoli® Storage Manager client to manage the scheduler process using the Tivoli Storage Manager client acceptor daemon.

The client acceptor daemon provides a light-weight timer which automatically starts and stops the scheduler process as needed. Alternatively, the traditional method keeps the Tivoli Storage Manager scheduler process running continuously. Generally, using the client acceptor daemon to manage the scheduler is the preferred method.

The following information is a comparison of the client acceptor daemon-managed services and the traditional scheduler services methods.

Client acceptor daemon-managed services

• Defined using the managedservices schedule option and started with client acceptor daemon services (dsmcad).
• The client acceptor daemon starts and stops the scheduler process as needed for each scheduled action.
• Requires fewer system resources when idle.
• Tivoli Storage Manager client options and Tivoli Storage Manager server override options are refreshed each time the client acceptor daemon services start a scheduled backup.
• Cannot be used with SESSIONINITiation=SERVEROnly backups.

Tivoli Storage Manager traditional scheduler services

• Started with command dsmc sched command.
• Remains active, even after scheduled backup is complete.
• Requires higher use of system resources when idle.
• Tivoli Storage Manager client options and Tivoli Storage Manager server override options are only processed once when dsmc sched is started; if you delete an option from a client options set, you must restart the scheduler so the scheduler is made aware of the deletion.

Tip: Restart the traditional scheduler periodically to free system resources previously used by system calls.