Configuration - DB2 MultiNode iDataAgent

The DB2 MultiNode pseudo-client and its corresponding instance serve as a logical grouping of DB2 MultiNode database partitions that are housed on various clients. The pseudo-client is not automatically created in the CommCell Browser by the software. Once the DB2 MultiNode iDataAgent is installed, you must create and configure the DB2 MultiNode pseudo-client.

Creating a DB2 MultiNode Pseudo Client

When you create a DB2 MultiNode pseudo-client, a DB2 MultiNode partition instance is also created at the same time. Each pseudo-client can include only this one partition instance; you cannot create additional instances for any one pseudo-client. To create additional partition instances, you must create additional pseudo-clients.

Use the following steps to configure a DB2 MultiNode pseudo-client.

  1. From the CommCell Console, right-click the Client Computers, point to New Client, and then click DB2 MultiNode.
  2. On the Create DB2 MultiNode Client dialog:
    • Enter the Client Name.
    • Enter the Instance Name.
    • Click the Change button under User Account.
    • Enter the DB2 User Account, Password and Confirm Password on the Set DB2 User Account dialog.  Click OK.
  3. Navigate to the Details tab of the Create DB2 MultiNode Client dialog:
    • Enter the path to the Home directory.  Use the Browse button to navigate to it.
    • Select the Client.

    In a DB2 DPF configuration, all clients are listed.

    In a DB2 pureScale configuration, only member clients are listed.

  4. Navigate to the Storage Device tab of the Create DB2 MultiNode Client dialog.

    On the Data Backup tab, select the Default Storage Policy.  If there is not one configured, see Step 5.

  5. Navigate to the Command Line Backup tab and select the Storage Policy for Command Line Backup.  If there is not one configured, see Step 5.

    Navigate to the Log Backup tab and select the Storage Policy for All Log Files. 

  6. Create a Storage Policy.
    1. Click Create Storage Policy.
    2. Follow the prompts displayed in the Storage Policy Wizard. The required options are mentioned below:
      1. Select the Storage Policy type as Data Protection and Archiving and click Next.
      2. Enter the name in the Storage Policy Name box and click Next.
      3. From the Library list, click the name of a disk library to which the primary copy should be associated and then click Next.

        Ensure that you select a library attached to a MediaAgent operating in the current release.

      4. From the MediaAgent list, click the name of a MediaAgent that will be used to create the primary copy and then click Next.
      5. For the device streams and the retention criteria information, click Next to accept default values.
      6. Select Yes to enable deduplication for the primary copy.
      7. From the MediaAgent list, click the name of the MediaAgent that will be used to host the Deduplication database (DDB).

        In the Location box, type the name of the folder in which the DDB must be located or click the Browse to select the folder, and then click Next.

      8. Review the details and click Finish to create the Storage Policy.
  7. Configure the following parameters to back up any type of DB2 data online or offline, update the database configuration parameters on each DB2 MultiNode partitions when DB2 agent is installed on a cluster or multiple instances of SnapProtect.

    For DB2 DPF

    Run the following DB2 commands on each DB2 DPF node.

    1. From the DB2 Console, enter the command to set the LOGARCHOPT1 parameter.

      db2 update db cfg for <database name> DBPARTITIONNUM (n) using LOGARCHOPT1 "'CvClientName=<DB2ClinetNameOnNode(n)>,CvDpfClientName=<Db2MultiNode_PesudeoClientName>,CvInstanceName= <Simpana_InstanceName>'"

    2. Enter the command to set the VENDOROPT parameter.

      db2 update db cfg for <database name> DBPARTITIONNUM (n) using VENDOROPT "'CvClientName=<DB2ClinetNameOnNode(n)>,CvDpfClientName=<CvClientName> <Db2MultiNode_PesudeoClientName>,CvInstanceName= <Simpana_InstanceName>'"

     For DB2 pureScale

    1. From the DB2 Console, enter the command to set the LOGARCHOPT1 parameter.

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

    2. Enter the command to set the VENDOROPT parameter.

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

Where

<database_name> = DB2 Database Name which you want to configure for Backup

(n) = DB2 Node Number of DB2 DPF. This does not apply to DB2 pureScale.  Get this value by looking at column 1 in the db2nodes.cfg file.

cat db2nodes.cfg
0 db2dpfvm1 0 
1 db2dpfvm2 0
2 db2dpfvm3 0
3 db2dpfvm4 0

CvClientName = DB2 Client Name

CvDpfClientName = DB2 DPF Pesudeo Client Name in the SnapProtect CommServe

CvInstanceName =  SnapProtect Instance Name in DB2 Client ( for example, Instance001)

VENDOR:/opt/simpana/Base/libDb2Sbt.so =  SnapProtect SBT library