Two types of configuration are available in a DB2 system:
In a hot standby configuration, one machine in the Solstice HA 1.3 cluster provides dedicated backup support, and another machine participates in the partitioned database system. If the machine participating in the database system fails, the database partition server on it will be started on the backup machine. If you are running multiple logical nodes on a machine and it fails, the logical nodes will be started on the backup machine. Figure 13 shows an example of a hot standby configuration.
Figure 13. Hot Standby Configuration for Solstice HA 1.3
In a mutual takeover configuration, both machines participate in the database system (that is, each machine has at least one database partition server running on it). If one of the machines in the cluster fails, the database partition server on the failing machine will be started to run as a logical node (or logical nodes) on the other machine. In a mutual takeover configuration, a database partition server on one machine can fail independently of the database partition server on another machine. Any database partition server can be active on any machine at any given point in time. Figure 14 shows an example of a mutual takeover configuration.
Figure 14. Mutual Takeover Configuration for Solstice HA 1.3
[ DB2 List of Books | Search the DB2 Books ]