IBM Tivoli Storage Manager for Mail, Data Protection for Microsoft Exchange Server, Version 7.1

Scheduling

Review these characteristics when you are defining a Tivoli® Storage Manager schedule.

If you use the Tivoli Storage Manager server-prompted scheduling mode, ensure that the Data Protection for Exchange option file has the tcpclientaddress and tcpclientport options specified. If you want to run more than one scheduler service, use the same tcpclientaddress. However, you must use different values for tcpclientport (in addition to the different node names). An example of running more than one scheduler service is when you schedule Data Protection for Exchange and the regular Windows backup client.
Server-prompted scheduling is supported only when TCP/IP communication is being used. By default, Data Protection for Exchange uses the client polling schedule mode.
If any changes that affect the scheduler are made to the Data Protection for Exchange options file, restart the scheduler to activate the changes. Examples of what can affect the scheduler are the Tivoli Storage Manager server address, the schedule mode, or the client TCP address or port. To restart the scheduler, issue the following commands:
```
  net stop "Data Protection for Exchange Scheduler"  
  net start "Data Protection for Exchange Scheduler" 
```
The default Tivoli Storage Manager scheduler log file (dsmsched.log) contains status information for the Tivoli Storage Manager scheduler. In this example, the file is in this path:
```
d:\Program Files\Tivoli\TSM\TDPExchange\dsmsched.log
```
You can override this file name by specifying the schedlogname option in the Data Protection for Exchange options file.
Data Protection for Exchange creates a log file with statistics about the backed up database objects when the /logfile parameter is specified during the tdpexcc command. Outputs from the scheduled commands are sent to the scheduler log file (dsmsched.log). After scheduled work is completed, check the log to verify that the work is completed successfully.
When a scheduled command is processed, the scheduler log might contain the following entry:
```
  Scheduled event eventname completed successfully
```
This result is an indication that Tivoli Storage Manager successfully issued the scheduled command that is associated with the eventname. No attempt is made to determine the success or failure of the command. Assess the success or failure of the command by evaluating the return code from the scheduled command in the scheduler log. The scheduler log entry for the command's return code is prefaced with the following text:
```
  Finished command. Return code is:
```
If any scheduled backups fail, the scheduler script exits with the same error code as the failed backup command. A non-zero error code means that the backup failed.
If passwordaccess generate is not specified in the dsm.opt file, then the Tivoli Storage Manager password is to be specified on the tdpexcc command. To specify the password, use the /tsmpassword parameter in the command file that is being run by the scheduler (excfull.cmd). You can also specify the password on the Data Protection for Exchange command line. For example:
```
tdpexcc query tsm /tsmnode=mars1 /tsmpassword=newpassword
```

Feedback