DB2 High Availability
High availability is about ensuring that a database system or other critical server functions remain operational both during planned or unplanned outages, such as maintenance operations, or hardware or network failures. Reduced database down-time enables you to meet strict Service Level Agreements (SLAs) with no loss of data during infrastructure failures.
DB2 provides database clustering as well as high availability and disaster recovery capabilities designed to maximize data availability during both planned and unplanned events. It also allows you to quickly and easily adapt to changing workloads with minimal involvement from database administrators, and frees application developers from the underlying complexities of database design and architecture.
DB2 high availability disaster recovery (HADR) feature provides a high availability solution for both partial and complete site failures. HADR protects against data loss by replicating data changes from a source or the primary server, to one or more standby servers. DB2 HADR supports up to three remote standby servers and is available in all DB2 editions excluding DB2 Express-C.
IBM® DB2® pureScale® helps change the economics of continuous data availability. DB2 pureScale is designed for organizations that require high availability, reliability and scalability for online transaction processing (OLTP) to meet stringent service level agreements. Broad choices for underlying infrastructure and flexible licensing terms help deliver high service levels at an attractive price point.
Bring it all together
In the event of unplanned downtime, DB2 pureScale and HADR are designed to failover in seconds 1. HADR can also help disaster recovery of pureScale clusters over distance of 1000s km 1. Together, DB2 pureScale and HADR reduce the risks of planned and unplanned outages to help meet your SLA requirements.
1 Based on IBM design for normal operation under typical workload using DB2 10.5 HADR and pureScale clusters. Individual results will vary depending on individual workloads, configurations and conditions, network availability and bandwidth.