Loading...

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, ensure that no applications are currently using the database. Also, consult your database administrator about the business requirements for the database.

Update the database configuration parameters when the DB2 agent is installed on a cluster, or when you have multiple CommCell Console instances.

Note: After you modify the LOGARCHMETH1 parameter, you must perform an offline full backup. When you do this, the DB2 software moves the database out of the state.

About This Task

When the DB2 instance is running on non-cluster configuration and you use the default SnapProtect instance (Instance001), you do not need to update the VENDOROPT and LOGARCHOPT1 parameters.

After you change the TRACKMOD database configuration parameter, run an offline full backup to update the parameter.

Use the following parameters when you use the VENDOROPT and LOGARCHOPT1 parameters.

Parameter Description
database_name The DB2 database name
CvClientName The name of the client in the CommCell Console

When you have a clustered environment, you must set this parameter to the virtual client name in the CommCell Console.

CvInstanceName The name of the SnapProtect installed instance
software_install_path The path where the agent software is installed

For non-Linux UNIX agents, use base64 for 64-bit machines and base32 for 32-bit machines.

For Linux, use base.

DvDpfClientName The DB2 MultiNode pseudo-client.
n

The DB2 Node Number. This does not apply to DB2 pureScale.  Get this value by looking at column 1 in the db2nodes.cfg file.

Example

cat db2nodes.cfg
0 db2dpfvm1 0 
1 db2dpfvm2 0
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

    db2 update db cfg for database_name DBPARTITIONNUM (n) using LOGARCHOPT1 "'CvClientName=DB2ClinetNameOnNode(n),CvDpfClientName=Db2MultiNode_PesudeoClientName,CvInstanceName=SnapProtect_InstanceName'"

    DB2 pureScale

    db2 update db cfg for database name using LOGARCHOPT1 "'CvDpfClientName=Db2MultiNode_PesudeoClientName,CvInstanceName=SnapProtect_InstanceName'"

Set the VENDOROPT Parameter

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

    DB2 DPF

    db2 update db cfg for atabase_name DBPARTITIONNUM (n) using using VENDOROPT "'CvClientName=DB2ClinetNameOnNode(n),CvDpfClientName=Db2MultiNode_PesudeoClientName,CvInstanceName=SnapProtect_InstanceName'"

    Example:

    db2 update db cfg for database name using VENDOROPT "'CvDpfClientName=Db2MultiNode_PesudeoClientName,CvInstanceName=SnapProtect_InstanceName'"

Examples

Set the Parameter for Delta or Incremental Backups

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

Note: You must set the TRACKMOD database configuration parameter to 'on' when you run a full backup before the delta backup or incremental backup.

DB2 DPF

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

DB2 pureScale

db2 update database configuration for test_database 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 log files are deleted from the threshold directory. 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 the log files are transferred to tape.

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.

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

    For DB2 DPF with USEREXIT

    db2 update db cfg for database name DBPARTITIONNUM (n) using USEREXIT on

    For DB2 DPF with LOGARCHMETH1

    db2 update db cfg for <database name DBPARTITIONNUM (n) using LOGARCHMETH1 "'VENDOR:/opt/SnapProtect/Base/libDb2Sbt.so'"

    For DB2 pureScale with LOGARCHMETH1

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