HP Serviceguard Toolkits for Database Replication Solutions User Guide, March 2012

3 Serviceguard toolkit for DB2 High Availability Disaster
Recovery
Overview
The HP Serviceguard toolkit for DB2 High Availability Disaster Recovery (DB2 HADR toolkit) enables
you to configure the DB2 primary and standby database as two Serviceguard packages. It provides
high availability for DB2 database and role management assistance, such as role takeover and
role switch for DB2 HADR.
DB2 HADR toolkit handles role takeover automatically. When the primary database fails, standby
package performs a role takeover. This process is faster than the entire process of stopping the
database on one node and starting it on another node.
After role takeover, when the primary package is started, the database starts as standby because
the primary database is already up. In this scenario, the standby package runs as a primary
database and the primary package runs as a standby database. DB2 HADR toolkit can also be
configured to perform a role switch to restore the configured role.
Advantages
When DB2 HADR is deployed in an HP Serviceguard cluster using DB2 HADR toolkit, it has the
following advantages:
• Provides high availability for DB2 processes, for both primary and the standby database.
• Provides seamless role takeover and role switch features between databases both in the same
and different clusters.
• You can configure the packages using Serviceguard Manager. For more information, see
http://www.hp.com/go/hpux-serviceguard-docs → HP Serviceguard Manager.
Dependencies
DB2 HADR toolkit requires the Enterprise Cluster Master Toolkit (ECMT) DB2 Toolkit.
Prerequisites
This section lists the prerequisites for DB2 HADR toolkit.
• Serviceguard A.11.20 must be installed on all nodes and the cluster must be configured.
• Enterprise Cluster Master Toolkit version B.06.00 or later must be installed.
• DB2 v9.7 with Fix Pack 4 must be installed. The database must be created, and HADR must
be configured for that database. Both standby and primary HADR must be started before
starting DB2 HADR packages.
• Secure Shell (SSH) connection without password for root user must be set between the nodes
on which the primary and standby packages are configured. The connection must be set using
the interconnect traffic IP address or alias name used to configure DB2 HADR. For steps on
how to configure SSH connection, see “ To configure SSH connection without password for
root user between two nodes” (page 56)
• DB2 HADR must be configured using the same DB2 instance name on both primary and the
standby database.
• For separate packaging, ECMT DB2 package must be created before creating the HADR
packages.
For more information on Separate Packaging, see “Packaging methods” (page 36)
34 Serviceguard toolkit for DB2 High Availability Disaster Recovery