Tivoli Storage Manager for Windows: Administrator's Guide


Overview of the Tivoli Storage Manager Scheduler Running as a Windows Service

Client nodes on Windows systems run scheduled operations through the TSM Scheduler, as do other client nodes. However, client nodes on Windows benefit from running the TSM Scheduler as a service. This feature allows the TSM Scheduler to run as a protected account, but does not require you to be logged on to run the service.

Figure 54 shows three Windows machines configured for scheduling.

Figure 54. Overview of the TSM Scheduler as a Windows Service

Overview of the TSM Scheduler as a Windows Service

Machine 1 -- Remote Client
Machine 1 contains only a backup-archive client. It has been configured to back up its file system to the server on Machine 4. The TSM Scheduler has been configured. The client uses the information in the client options file (dsm.opt) to connect to the server. The client options file contains the server address of the server (Machine 4).

Machine 2 -- Tivoli Data Protection application client
Machine 2 contains an application client and a backup-archive client. Note that the backup-archive client is not connected to the server. The backup-archive client on Machine 2 has been installed only to provide access to the DSMCUTIL utility, not to back up the resident file system. After the backup-archive client has been used to install the scheduler, it may continue to be required for updating the password or other scheduling service parameters. The application client uses the information in its client options file to connect to the server.

Machine 3 -- Tivoli Data Protection application client and backup-archive client on the same machine
Machine 3 contains an application client and a backup-archive client. The application client backs up databases and transaction logs to the server. The backup-archive client backs up other files on Machine 3's file system, including the database administrator's online documentation and performance records. The scheduler wizard is used to install a scheduler service for the backup-archive client and a second scheduler service for the application client. The two clients use the information in their client options files to connect to the server.

Machine 4 -- Server and local backup-archive client on the same machine
Machine 4 contains a server and a local backup-archive client. For this client (packaged with the TSM server), the scheduler is configured during setup, and the administrator need only update the password.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]