Introduction
Enterprise applications need a continuously available data source to keep workflows operating at maximum efficiency. Any downtime due to a localized disaster can leave mission-critical databases inaccessible. Minimizing your outage time and data loss isn't just a business requirement; it's a business necessity.
This article outlines the setup and operation of a disaster recovery (DR) solution for DB2 V10.5 databases on the IBM PureData System for Transactions, Fix Pack 3 or later. The solution is based on the DB2 High Availability and Disaster Recovery (HADR) feature and includes additional elements that are not handled directly by the HADR feature. HADR replicates any data changes from a primary database source to a standby database target. This technology is fully integrated into DB2 and uses a standard TCP/IP network interface between the primary and standby database systems. HADR provides fast takeover operations for both planned and unplanned events.
HADR in the IBM PureData System for Transactions is designed to provide disaster recovery at the system, instance, and database levels. This solution requires two PureData System for Transactions systems. System takeover is implemented manually through high availability and disaster recovery commands and can be integrated into your enterprise strategy for disaster recovery.
This scenario covers the entire lifecycle: setup, normal operations, and conducting a takeover.
Download the full report for more on implementing disaster recovery in IBM PureDataSystem for Transactions.
Download the report to get started!
#Db2