V11 SP8
Loading...

Configuration - FlexFrame for DB2

Configuration

Once the DB2 iDataAgent has been installed, create virtual client using cluster client configuration from the CommCell Console.

Then configure an instance and a Backup Set to facilitate backups. Each Backup Set references a DB2 database.

The following sections provide the necessary steps required to create and configure these components for a first backup of a DB2 database.

Configuring the Cluster Group Client

After installing the software successfully on all the physical nodes that host the cluster group, you must configure the cluster group client from the CommCell Console. Use the following steps to configure the cluster group client.

  1. From the CommCell Browser, right-click the Client Computers node, point to New Client | Clustered Server and then click Unix Cluster.

  2. In the Client Name box, type a name for the cluster group. The client name can be any unique name.

    In the Host Name box, you can type either the fully qualified domain name of the cluster group or the IP address of the cluster group.

    • The Host name of the cluster group client should not be used by any existing client in your CommCell.
    • If you want to specify the IP address of the cluster group, ensure that the IP address is static.

  3. Review the cluster group information and click Finish.

    The Advanced Client Properties dialog box is displayed.

  4. On the Advanced Client Properties dialog box, click the Cluster Group Configuration tab.
    • All the Linux clients that are available in the CommCell will be listed in the Available list. Select the physical computers (nodes) where you installed the necessary agents from the Available list, and then click Add > to move the client to the Selected list.
    • Click the Agents tab.
      Select the agents you want to use in the cluster group client from the Available list and click Add > to move the Agent to the Selected list.

    If the client computer properties dialog box is not displayed automatically, then you need to open it manually: Right-click the  <Cluster Group Client>, and then click Properties. Click Advanced on the Client Computer Properties dialog box. Click Cluster Group Configuration tab on the Advanced Client Properties dialog box.

  5. Click the Agents tab.

    Select the agents you want to use in the cluster group client from the Available list and click Add > to move the agent to the Selected list.

    In order to configure a Cluster Group Client, the agents should be installed on all the clustered nodes for proper failover. If an agent is not installed on all the nodes, then the agents selection tab on the Advanced Client Properties window will display the agent name in plain text (not in bold). However, you can still configure the Cluster Group Client even when the Agents are not installed on a particular node; installation can be done later using remote install procedure.

  6. Click the Job Configuration tab.

    In the Job Results Directory box, type the path for the job results directory. Ensure that the directory resides on a shared clustered file system.

    • The Browse button does not work when you configure the cluster group client for the first time. After the initial configuration, you can use the button to update the directory (if required).
    • In the case of MediaAgent and ContinuousDataReplicator, the Job Result directory path will be used for both the Index Cache and CDR Log directories respectively unless another directory location is provided.

    Click OK.

  7. Click OK.

    The cluster group client is successfully created.

  • Ensure that the path provided for the Job Results Directory is an absolute path.

    For example, /addon/ commvault_pool/job_results/p22-dbsm1-se

  • If MediaAgent is installed on a physical node, ensure that the path provided for Index Cache is an absolute path. Else, post installation, edit the MediaAgent properties to provide a different path for Index Cache.

DB2 Configuration

  1. Use the following steps to configure DB2:

    Automatically Updating DB2 Parameters

    You can automatically update DB2 parameters (LOGARCHMETH1, LOGARCHOPT1, VENDOROPT, TRACKMOD, etc.,) using Db2_config.sh to perform backups and restores. See Can we automatically update DB2 parameters? for more information.

    You can manually update the db2 parameter LOGARCHMETH1

    From the DB2 console, type the following command to update the LOGARCHMETH1 parameter:

    >db2 update db cfg for <database name> using LOGARCHMETH1 "'VENDOR:/commvault_install_path/Base/libDb2Sbt.so'"

    Example:

    >db2 update db cfg for test_db using LOGARCHMETH1 " '/db_installs/Base/libDb2Sbt.so' "

    commvault_install_path is the path of Commvault installation location.

    Use Base or Base64 for Linux operating system:

    Unix:

    >db2 update db cfg for <database name> using LOGARCHMETH1 "'VENDOR:/commvault_install_path/Base64/libDb2Sbt.so'"

    Example:

    >db2 update database configuration for testdb using LOGARCHMETH1 "VENDOR:D:\CommVault\ContentStore\Base\DB2Sbt.dll"

    DB2 Configuration on Cluster

    This configuration is required only if you install Commvault on cluster and DB2 is running on a virtual computer.

    Type the following command to configure the VENDOROPT parameter:

    >db2 update db cfg for <database name> using VENDOROPT "'CvClientName=<Your_DB2_Client_Name>,CvInstanceName=<Your_Commvault_Instance_Name>'"

    Type the following command to configure the LOGARCHOPT1 parameter:

    >db2 update db cfg for <database name> using LOGARCHOPT1 "'CvClientName=<Your_DB2_Client_Name>,CvInstanceName=<Your_Commvault_Instance_Name>'"

    For Delta or Incremental Backups

    From the DB2 Console, type the following commands in the below mentioned sequence to enable the TRACKMOD database configuration parameter and perform incremental or delta DB2 backups.

    db2 update db cfg for <database name> using TRACKMOD on

  2. From the CommCell Browser, navigate to Client Computers | <Client>.

    Right-click DB2, point to All Tasks, and then click Discover Instances.

    You must configure the instances using Discover Instances in order to use the auto instance discovery. You should have the DB2 Administrative privileges to configure the instances.

  3. In the confirmation dialog box, click Yes.
  4. Right-click the <Instance>, and then click Properties.

  5. In the DB2 User Account box, Click Change and type the user name to access the DB2 application.

    In the Password box, type the password for the user account.

    In the Confirm Password box, retype the password for the user account.

    Click OK.

  6. Click the Storage Device tab and associate the storage policies for Data/Log/command line backups.

    If you do not find any associated storage policies in the Default Storage policy box, then follow the steps given in step 16 to create a Storage Policy.

    If you want to select a storage policy other than default storage policy, then, in the Default Storage Policy box, select the storage policy. Refer the storage policy rules applicable for DB2 instance.

  7. Click the Command Line Backup tab.

    In the Storage Policy for Command Line Backup box, select a storage policy name.

    If you do not have a Storage Policy created, follow the steps given in step 16 to create a Storage Policy.

  8. Click the Logs Backup tab.

    In the Storage Policy for All Log Files box, select a storage policy name.

    If you do not have a Storage Policy created, follow the steps given in step 16 to create a Storage Policy.

    Click OK.

  9. Click OK to save the Instance properties.
  10. From the CommCell Browser, navigate to Client Computers | <Client> | DB2.

    Right-click the <Instance>, point to All Tasks, and then click Discover Databases.

    .

  11. Click Yes.

  12. If the databases are discovered, backupsets with the name of the discovered database(s) will be listed under the DB2 instance. If the databases are discovered, then skip the below steps and go to step 13.

    If the databases are not discovered, then you have to create a new backup set.

    From the CommCell Browser, navigate to Client Computers | <Client> | DB2.

    Right-click the <Instance>, point to All Tasks, and then click Create New Backup Set.

  13. Select the desired database from the available databases listed under the Available DB Names, and then click the arrow " >" button to move the selected database into Selection box.

    In the Storage Policy for all Log Files box, select the storage policy name.

    Click OK.

  14. From the CommCell Browser, navigate to Client Computers | <Client> | DB2 | <Instance> | <Backup Set>.

    Right-click the <Subclient>, and then click Properties.

  15. Click the Storage Device tab.

    In the Data Storage Policy list, select a Storage Policy name.

    Click OK.

  16. If you do not have Storage Policy created, follow the steps given below to create a storage policy.
    1. From the CommCell Browser, navigate to Policies.
    2. Right-click the Storage Policies and then click New Storage Policy.
    3. Follow the prompts displayed in the Storage Policy Wizard. The required options are mentioned below:
      • Select the Storage Policy type as Data Protection and Archiving and click Next.
      • Enter the name in the Storage Policy Name box and click Next.
      • 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.

      • From the MediaAgent list, click the name of a MediaAgent that will be used to create the primary copy and then click Next.
      • For the device streams and the retention criteria information, click Next to accept default values.
      • Select Yes to enable deduplication for the primary copy.
      • 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 button to select the folder and then click Next.

      • Review the details and click Finish to create the Storage Policy.