Setting the DB2 MultiNode Configuration Parameters

Each DB2 MultiNode database has its own configuration. To back up DB2 data successfully, you must enable the appropriate database configuration parameters. You must set these parameters based on the state of the database, the backup type, and/or the data type.

Before you change any configuration parameter, verify that no applications are currently using the database.

Use the following Commvault parameters when you use the DB2 VENDOROPT, LOGARCHOPT1 and TRACKMOD parameters.

dcat db2nodes.cfg
 0 db2dpfvm1 0 
 1 db2dpfvm1 1 
 2 db2dpfvm3 0 
 3 db2dpfvm4 0

Procedure

Set the LOGARCHOPT1 Parameter

• From the DB2 console, type the following command to set the LOGARCHOPT1 parameter:

  DB2 DPF

  You must run this command on each DB2 partition number node.

   
  db2 update db cfg for database_name DBPARTITIONNUM (n) using LOGARCHOPT1 "'CvClientName=DB2ClientName, CvInstanceName=InstanceName,CvDpfClientName=DB2MultiNode_PesudeoClientName'"

  DB2 pureScale

   
  db2 update db cfg for database_name using LOGARCHOPT1 "'CvInstanceName=InstanceName,CvDpfClientName=DB2MultiNode_PesudeoClientName'"

Set the VENDOROPT Parameter

• From the DB2 console, type the following command to set the VENDOROPT parameter:

  DB2 DPF

  You must run this command on each DB2 partition number node.

   
  db2 update db cfg for database_name DBPARTITIONNUM (n) using VENDOROPT "'CvClientName=DB2ClientName, CvInstanceName=InstanceName,CvDpfClientName=DB2MultiNode_PesudeoClientName'"

  DB2 pureScale

   
  db2 update db cfg for database_name using VENDOROPT  "'CvInstanceName=InstanceName,CvDpfClientName=DB2MultiNode_PesudeoClientName'"

Enable Delta and Incremental Backups

From the DB2 console, type the following command to set the TRACKMOD database configuration parameter:

DB2 DPF

You must run this command on each DB2 partition number node.

 
db2 update database configuration for database_name DBPARTITIONNUM (n) using TRACKMOD on

DB2 pureScale

 
db2 update database configuration for database_name using TRACKMOD on

Set the Parameter for Log Backups

The SBT interface transfers the log files from the DB2 directory to the threshold directory that you defined when you installed the DB2 Agent. If you use the delete option, then the software deletes the log files from the threshold directory after a successful backup. If you do not use the delete option, then the log files are kept in this directory. By default, the threshold directory can hold 1000 log files. If the threshold directory attempts to hold more than 1000 log files, then a command line backup for the log files starts automatically, and after the log files are transferred to tape, the software deletes the log files from the threshold directory.

You can change the log threshold. For more information, see Modifying the Threshold for Log Backups. We recommend that you set the value to 25 so that you can make optimal use of your resources.

Set this value to 1 to trigger the software to immediately perform a backup of each archive log, and then move the backup directly to media without transferring the file to the threshold directory.

• From the DB2 console, type the command to set the LOGARCHMETH1 database configuration parameter:

  You must run this command on each DB2 partition number node.

   
  db2 update db cfg for database_name DBPARTITIONNUM (n) using LOGARCHMETH1 "'VENDOR:software_install_path/libDb2Sbt.so'"

  For DB2 pureScale with LOGARCHMETH1

   
  db2 update db cfg for database_name using LOGARCHMETH1 "'VENDOR:software_install_path/libDb2Sbt.so'

Examples

DB2 DPF

The following table defines the parameter values for the example.

Run the following commands on each DB2 DPF node:

db2 update db cfg for TESTDB DBPARTITIONNUM 0 using LOGARCHMETH1 "'VENDOR:/opt/commvault/Base/libDb2Sbt.so'"
db2 update db cfg for TESTDB DBPARTITIONNUM 1 using LOGARCHMETH1 "'VENDOR:/opt/commvault/Base/libDb2Sbt.so'"
db2 update db cfg for TESTDB DBPARTITIONNUM 2 using LOGARCHMETH1 "'VENDOR:/opt/commvault/Base/libDb2Sbt.so'"
db2 update db cfg for TESTDB DBPARTITIONNUM 3 using LOGARCHMETH1 "'VENDOR:/opt/commvault/Base/libDb2Sbt.so'"
db2 update db cfg for TESTDB DBPARTITIONNUM 0 using LOGARCHOPT1 "'CvClientName=db2dpfvm1,CvInstanceName=Instance001,CvDpfClientName=DB2DPF_PART1051'"
db2 update db cfg for TESTDB DBPARTITIONNUM 1 using LOGARCHOPT1 "'CvClientName=db2dpfvm1,CvInstanceName=Instance001,CvDpfClientName=DB2DPF_PART1051'"
db2 update db cfg for TESTDB DBPARTITIONNUM 2 using LOGARCHOPT1 "'CvClientName=db2dpfvm3,CvInstanceName=Instance001,CvDpfClientName=DB2DPF_PART1051'"
db2 update db cfg for TESTDB DBPARTITIONNUM 3 using LOGARCHOPT1 "'CvClientName=db2dpfvm4,CvInstanceName=Instance001,CvDpfClientName=DB2DPF_PART1051'"
db2 update db cfg for TESTDB DBPARTITIONNUM 0 using VENDOROPT "'CvClientName=db2dpfvm1,CvInstanceName=Instance001,CvDpfClientName=DB2DPF_PART1051'"
db2 update db cfg for TESTDB DBPARTITIONNUM 1 using VENDOROPT "'CvClientName=db2dpfvm1,CvInstanceName=Instance001,CvDpfClientName=DB2DPF_PART1051'"
db2 update db cfg for TESTDB DBPARTITIONNUM 2 using VENDOROPT "'CvClientName=db2dpfvm3,CvInstanceName=Instance001,CvDpfClientName=DB2DPF_PART1051'"
db2 update db cfg for TESTDB DBPARTITIONNUM 3 using VENDOROPT "'CvClientName=db2dpfvm4,CvInstanceName=Instance001,CvDpfClientName=DB2DPF_PART1051'"
db2 update db cfg for TESTDB DBPARTITIONNUM 0 using TRACKMOD on 
 db2 update db cfg for TESTDB DBPARTITIONNUM 1 using TRACKMOD on 
 db2 update db cfg for TESTDB DBPARTITIONNUM 2 using TRACKMOD on 
 db2 update db cfg for TESTDB DBPARTITIONNUM 3 using TRACKMOD on

DB2 PureScale

The following table defines the parameter values for the example.

Run the following commands:

db2 update db cfg for PSDB1 using LOGARCHMETH1 "'VENDOR:/opt/commvault/Base/libDb2Sbt.so'" 
 db2 update db cfg for PSDB1 using LOGARCHOPT1 "'CvInstanceName=Instance001,CvDpfClientName= DB2pureScale_PS1051'" 
 db2 update db cfg for PSDB1 using VENDOROPT "'CvInstanceName=Instance001,CvDpfClientName= DB2pureScale_PS1051'" 
 db2 update db cfg for PSDB1 using TRACKMOD on