512 Getting Started with IBM Tivoli Workload Scheduler V8.3
򐂰 Pros
From outside the cluster, a failover has no impact. Everything continues
running with almost no impact on service.
򐂰 Cons
The standby nodes are completely idle (from a Tivoli Workload Scheduler
viewpoint) when all active nodes are operational.
This scenario was tested on systems running Red Hat Enterprise Linux AS 4.0,
and is applicable to most versions of Linux and AIX with only a few minor
11.2.2 Scenario 2: Switching domain managers
In this scenario, which is shown in Figure 11-2 on page 513, there are no
standby nodes. Instead, certain set of active Tivoli Workload Scheduler masters
can be switched over to certain set of backup masters. The mirroring of the
object databases is handled by the standard high availability disaster recovery
(HADR) function provided in DB2 Universal Database V8.2 Enterprise Server
Edition (ESE), which is included with Tivoli Workload Scheduler 8.3, and the
switching of management functions is automated.

Get Getting Started with IBM Tivoli Workload Scheduler V8.3 now with the O’Reilly learning platform.

O’Reilly members experience live online training, plus books, videos, and digital content from nearly 200 publishers.