|
A highly available database is a key requirement for a highly available WebSphere solution. Enhancing database availability is critical for WebSphere and can be achieved utilizing software and hardware cluster solutions. However, simply making the database engine highly available does not necessarily create a HA solution. It is important to note that even in a WebSphere environment which employs a HA database there is still an interruption in service while a database is switched from a failed server to an available server. This section focuses on the options available to build a highly available DB2 cluster and the application code (client) implications within WebSphere for database high availability and covers:
![]() | Continuous availability |
![]() | Failover availability |
![]() | Client application code considerations |
The information found in this section is based on the developerWorks article An Overview of High Availability and Disaster Recovery for DB2 UDB by Monty Wright, which is available at:
http://www.ibm.com/developerworks/db2/library/techarticle/0304wright/ 0304wright.html