# Configure DB2 High Availability Disaster Recovery (HADR) Cluster Client

In a High Availability Disaster Recovery (HADR) environment, the data is continually replicated from the source (primary) database to the target (standby) database by using the DB2 transaction logs. If something happens to the primary database, then the standby database is immediately ready to take over for the primary database.

Note

If you are using Command Center, you can configure and manage the DB2 HADR feature.

Perform the following configuration procedure, backup procedure, and restore procedure to use DB2 HADR with the Commvault software:

## DB2 High Availability Disaster - DB2 Automated Failover Using the IBM Tivoli System Automation (TSA) with a Virtual IP Address

### Before You Begin

Make sure that you have configured all databases according to the IBM HADR specifications.

### Procedure

1. Install DB2 agent on participating nodes i.e. primary and standby servers. For more information, refer to Complete Databases Guided Setup for DB2.

   Note

   Once you add the DB2 server successfully, the DB2 instance is discovered under the node/client. You should not update any instance properties at node/client level as the operations related to instance should be performed at HADR cluster client level.

2. Configure DB2 instance on newly created cluster client. For more information, refer to Adding DB2 HADR Database Instance.

3. Configure DB2 database from Discover HADR DB2 Database or Add a DB2 database.

   Note

   - The DB2 HADR database is automatically discovered.

   - Regardless of whether DB2 databases are discovered automatically or manually, only those with the HADR role set to PRIMARY will be discovered.

4. Set DB2 Configuration Parameters for DB2 HADR Using IBM Tivoli System Automation (TSA) with a Virtual IP Address.

5. Perform an online Backup of DB2 Database.

×

Loading...