DB2 Agent Configuration Frequently Asked Questions

Do I need to configure any database parameters to manage the DB2 Archive Logs?

Yes. You need to configure the LOGARCHMETH1 and LOGARCHOPT1 parameters to manage DB2 Archive Logs using Commvault VENDOR Library interface.

db2 update db cfg for sample using LOGARCHMETH1 "'VENDOR:/opt/commvault/Base64/libDb2Sbt.so'"
db2 update db cfg for sample using LOGARCHOPT1 "'CvClientName=db2client,CvInstanceName=Instance001'"

Can we use the USEREXIT method instead of LOGARCHMETH1 Vendor method to manage the DB2 log files?

The USEREXIT method is deprecated beginning in DB2 version 9.5. You can use this method in DB2 versions prior to v9.5 (instead of the LOGARCHMETH1 method) to backup the DB2 log files.

From the DB2 Console, type the following command to set the USEREXIT parameter:

db2 update database configuration for database name using USEREXIT on

Can we automatically update DB2 parameters?

Yes. You can automatically update DB2 parameters (LOGARCHMETH1, LOGARCHOPT1, VENDOROPT, and TRACKMOD) using scripts. For information, see Configuration - Automatically Updating DB2 Parameters.

How can we interactively update DB2 parameters?

For information on interactively updating DB2 configuration parameters, see Setting the DB2 Configuration Parameters.

DB2 Configuration on a cluster

Type the following command to configure the VENDOROPT parameter:

db2 update db cfg for database name using VENDOROPT "'CvClientName=DB2_VM_Cluster_Client_Name,CvInstanceName=Commvault_Instance_Name'"

Type the following command to configure the LOGARCHOPT1 parameter:

db2 update db cfg for database name using LOGARCHOPT1 "'CvClientName=DB2_VM_Cluster_Client_Name,CvInstanceName=Commvault_Instance_Name'"

Where

database_name is the DB2 database name

DB2_VM_Cluster_Client_Name is the name of the DB2 VM cluster client

Commvault_Instance_Name is the name of the DB2 instance in the CommCell Console. The default is Instance001

Example

The active and passive nodes are test1 and test2.

The cluster VM name is testVM

The CvClientName is testVM.

db2 update db cfg for testdb using LOGARCHOPT1 "'CvClientName=testVM,CvInstanceName=Instance001'"

For Delta or Incremental Backups

From the DB2 Console, type the following command to enable the TRACKMOD database configuration parameter and perform incremental or delta DB2 backups.

db2 update db cfg for database_name using TRACKMOD on

After setting TRACKMOD to ON, you must run an offline full backup before an incremental backup can be taken on the tablespace.

Does Commvault support DB2 HADR on a pacemaker cluster?

Yes.

To configure DB2 HADR on a pacemaker cluster, perform the following steps:

Install the Commvault software on the setups that have a primary standby node and a principal standby node. On an auxiliary standby node, you don't need to install the Commvault software because DB2 HADR ships the logs internally.
Configure HADR cluster.
When creating the cluster client from the CommCell Console, you must use the virtual IP address of the cluster as the hostname.