Introduction
DB2 pureScale (for Linux, UNIX and Windows) is a shared disk architecture clustering technology, where multiple DB2 members process database requests against a single shared copy of the database. HADR for DB2 pureScale provides the functionality of failover (continuous availability) and disaster recovery with a copy of data in a standby member, respectively. We will go over the fundamentals of configurations/setup/environment most optimally from a client application standpoint.
Note: HADR for DB2 pureScale is supported from DB2 10.5 onward. The copying of data between the primary and standby database happens via transaction of log streams. The standby database replays the logs to sync the data.
The following image depicts HADR for DB2 pureScale connectivity between client applications and a data sharing group with HADR configuration. The clients could be stand-alone applications or middleware, such as WebSphere® Application Server, that utilize connectivity offered by the IBM Data Server Driver for JDBC and SQLJ to connect to a DB2 data sharing group. The primary database and standby cluster with three members each can be at different locations. HADR uses TCP/IP communication for shipping transaction logs, and the preferred replay member in the standby cluster receives and replays the logs.
Download the full report for more on configure parameters for IBM Data Server Driver for JDBC and SQLJ against HADR for DB2 pureScale.
Download the report to get started!#Db2