
78 HA Architectures & Capacity Planning with WebSphere Remote Server V6
Figure 4-8 displays failover to node2. Once the failover process is complete, all
the components run on node2. Tivoli System Automation mounts the DRBD
partition on the standby server, making all the data available for MQ and DB2
running on that server. Floating IP now points to the standby server. The standby
server becomes primary and starts servicing all the requests. At the same time,
node1 gets rebooted. Once node1 comes up after the reboot, it becomes the
standby node.
Figure 4-8 Failover to node2
The steps involved in setting up this configuration are described in Chapter ...