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

Using the DB2 HADR toolkit
Packaging methods
DB2 HADR toolkit packages can be configured in combined or separate way.
• Combined Packaging: This method of packaging is recommended if an instance comprises
only one database. In this method of packaging, a package consists of ECMT DB2 and DB2
HADR modules and manages (starts, stops and monitors) both the instance and the HADR.
• Separate Packaging: This method of packaging is recommended if an instance comprises
multiple databases. One package is created using the DB2 HADR toolkit to manage HADR
and another package is created using the ECMT DB2 toolkit to manage the instance. If one
database fails, it does not impact other packages. However, if the instance fails, all the
packages fail.
NOTE: The DB2 HADR package created using the separate packaging method must have
the "same-node up" dependency on the DB2 instance package.
Supported configuration
This section explains the supported configuration for DB2 HADR toolkit. It includes the configuration
under the following scenarios:
Combined packaging
When primary and standby packages are in the same cluster
Figure 12 Primary and Standby Packages in the Same Cluster
In this configuration, Figure 12 (page 36), DB2 primary database is configured in a volume group
shared between Node 1 and Node 2. The standby database is configured in a volume group
shared between Node 3 and Node 4. HADR is configured between primary and standby database.
The DB2 database and the HADR are packaged using the DB2 HADR toolkit.
Two separate packages are created; one each for primary and standby database. Primary package
is configured to run either on Node 1 or on Node 2 and is currently running on Node 2. If the
primary package fails on Node 2, then it fails over to Node 1. Similarly, the standby package is
36 Serviceguard toolkit for DB2 High Availability Disaster Recovery