IBM® DB2® server contains functionality that supports
many high availability strategies.
Automatic client reroute roadmap
Automatic client reroute is an IBM DB2 server
feature that redirects client applications from a failed server to
an alternate server so the applications can continue their work with
minimal interruption. Automatic client reroute can be accomplished
only if an alternate server has been specified prior to the failure.
DB2 fault monitor facilities for Linux and UNIX
Available on UNIX based
systems only, DB2 fault monitor
facilities keep IBM DB2 server databases up and running
by monitoring DB2 database manager
instances, and restarting any instance that exits prematurely.
High Availability Disaster Recovery (HADR)
The DB2 Data Server High Availability Disaster Recovery
(HADR) feature is a database replication feature that provides a high
availability solution for both partial and complete site failures.
HADR protects against data loss by replicating data changes from a
source database, called the primary, to a target database, called
the standby.
DB2 High Availability Feature The DB2 High Availability
Feature enables
integration between IBM DB2
server and cluster managing software.
High availability through log shipping
Log shipping is the process of copying whole
log files to a standby machine either from an archive device, or through
a user exit program running against the primary database. A scheduled
job on the standby issues the ROLLFORWARD DATABASE command
at a specified interval to keep the standby current in terms of log
replay.
Log mirroring
IBM DB2 server supports log mirroring at the
database level. Mirroring log files helps protect a database from
accidental deletion of an active log and data corruption caused by
hardware failure.
High availability through suspended I/O and online split mirror support
IBM DB2 server suspended
I/O support enables you to split mirrored copies of your primary database
without taking the database offline. You can use this to very quickly
create a standby database to take over if the primary database fails.