Configuring a clustered environment for high availability
Creating a cluster of machines, and using cluster managing software to balance
work load on those machines is one strategy for designing a highly available solution.
If you install IBM®
Db2® server on
one or several of the machines in a cluster, you must configure the cluster manager to properly
react to failures that affect the database or databases. Also, you must configure the database
manager instances to work properly in the clustered environment.
About this task
Configuring and administering the database instances and the cluster manager manually is complex, time consuming, and prone to error. The Db2 High Availability Feature provides infrastructure for enabling the database manager to communicate with your cluster manager when instance configuration changes, such as stopping a database manager instance, require cluster changes.
There
are two cluster manager products for implementing High Availability solution:
- Pacemaker: This cluster manager is used for Db2 on Linux. Please follow Configuring high availability with the Db2 cluster manager utility (db2cm) to configure your chosen High Availability solution on Linux.
- Tivoli SA MP: This cluster manager is used for Db2 on AIX. The task described below is specific to using Tivoli SA MP-managed Db2 instance on AIX.
Note: If you are using an AIX® system, consider enabling the
system error log (syslog) to capture relevant messages from Tivoli®SA MP and RSCT
subsystems and from the Db2 automation scripts.
For more information, see the Related links.