Designing your Tivoli Workload Scheduler for z/OS DRP

The complexity of your Tivoli Workload Scheduler for z/OS DRP depends on the recovery strategies of your business systems. The following sections explain the procedures for a Tivoli Workload Scheduler for z/OS recovery plan that best meets your business DRP strategies:

If your business uses more than one of these recovery strategies, your DRP should be designed for the most complex. Consider this example:

Under normal circumstances, the DP center handles the processing of six business systems. Only four of these systems provide off-site recoverability. Three of the four send backups off-site each hour; the other system creates backups only when processing is complete each day. The Tivoli Workload Scheduler for z/OS DRP required to support this environment must generate off-site backups each hour. After Tivoli Workload Scheduler for z/OS is recovered to the most recent backup in the secondary center, application occurrences for those systems that recover to start-of-day are reset to waiting status. Occurrences not required are deleted from the current plan.