Db2 or Db2 Warehouse high availability disaster recovery (HADR)

Db2 or Db2 Warehouse on Red Hat OpenShift supports Db2 high availability disaster recovery (HADR) to protect against data loss on various topologies, including primary and standby on the same or different Red Hat® OpenShift® clusters and within the same or different projects (namespaces).

HADR provides a high availability solution for both partial and complete site failures by replicating data changes from a source database, called the primary database, to the target databases, called the standby databases. Db2 or Db2 Warehouse on Red Hat OpenShift supports up to three remote standby servers.

Before you begin: To set up a Db2 or Db2 Warehouse HADR configuration on Red Hat OpenShift, you must install and deploy two or more Db2 or Db2 Warehouse database services that are at the same release level. Use the same database name for the deployed service instances.

Part of the setup process involves sharing the database backup image and keystore tar file between the primary and standby databases. If the databases are in the same OpenShift project in a single OpenShift cluster, it can be beneficial to use a backup volume that is shared between the primary and standby databases. In this case, you need to create the volume when you deploy Db2 or Db2 Warehouse. If the databases are on different OpenShift projects and/or clusters, the databases can be deployed without shared volumes, and you can use rsync to copy assets.

Restriction: HADR for multiple databases in a single Db2® deployment is not supported. To enable HADR for multiple databases, create separate deployments for each database.

For full HADR documentation, see High availability disaster recovery (HADR).