To configure your DB2® database
solution for high availability, you must: schedule database maintenance
activities; configure the primary and standby database servers to
know about each other and their respective roles in the event of a
failure; and configure any cluster managing software to transfer workload
from a failed cluster node.
Before you begin
Before configuring your database solution:
Assemble and install the underlying hardware and software components
that make up the solution. These underlying components might include:
power supply; network connectivity; network cards; disks or other
storage devices; operating systems; and cluster managing software.
Test these underlying components without any database workload
to make sure they are functioning properly before attempting to use
them in database load balancing, failover, or recovery operations.
About this task
Redundancy is an important part of a high availability solution.
However, if you do not schedule maintenance wisely, if you run out
of storage space for needed recovery logs, or if your cluster managing
software is not configured correctly, your solution might not be available
when your users need to do crucial work with the database.
Procedure
- Configuring automatic client reroute (ACR) ACR
seamlessly redirects client applications from a failed server to an
alternate server so that thee applications can continue their work
with minimal interruption.
- Configuring fault monitor DB2 fault monitor keeps DB2 instances up and running by monitoring them
and restarting them in the even of unexpected failures.
- Configuring DB2 high
availability disaster recovery (HADR) HADR protects you
against data loss and downtime from site failures by replicating data
changes from a primary database to a standby database.
- Scheduling maintenance activities Through careful
planning, automating, and scheduling your maintenance operations,
you can help maximize your database's availability.
- Configuring cluster managing software Cluster
managing software can help automate the transfer of database operations
from a failed primary database to a secondary or standby database.
- Configuring database logging options Use database
logging configuration parameters to specify data logging options for
your database, such as the type of logging to use, the size of the
log files, and the location where log files should be stored.