Advanced Configuration - DB2 MultiNode iDataAgent

Table of Contents

Understanding the CommCell Console

The DB2 MultiNode iDataAgent uses the following logical entities to manage backup and restore operations from the CommCell Console.

Instance

Defines the DB2 DPF or DB2 pureScale instance. It includes one or more partitioned databases.

Backup Set

Defines theDB2 DPF or DB2 pureScale database to be backed up.

Subclient

Defines the DB2 DPF or DB2 pureScale database objects to be backed up.

Managing Instances

DB2 MultiNode instances are created as part of the procedure to create a DB2 MultiNode pseudo-client, and they are used to add, modify, and configure multiple DB2 MultiNode databases and their partitions.

When you create a DB2 MultiNode pseudo-client, you also create a DB2 MultiNode partition instance at the same time. Each pseudo-client can include only this single partition instance. Once an instance is created, you cannot create additional instances for this pseudo-client. To create additional partition instances, you must create additional pseudo-clients. For more information, see Creating a DB2 MultiNode pseudo-client.

When you create an instance, the instance type (DB2 DPF or DB2 pureScale) is automatically configured based on the database type. 

When the instance is for a DB2 pureScale, only member clients are listed on the Details tab of the Instance Properties dialog.

Managing Backup Sets

For the DB2 MultiNode iDataAgent, each instance includes one or more database partitions that you want to back up. An instance can contain one or more backup sets, and a backup set can contain one or more subclients.

A backup set is a logical grouping of subclients. Backup sets are created based on the available DB2 DPF or DB2 pureScale databases. Each backup set is designed to represent a single database, and the backup set name is identical to the name of the database that the backup set represents. You cannot create multiple backup sets for a single DB2 DPF or DB2 pureScale database.

Each backup set includes one or more subclients. Whenever you create a backup set, the software automatically creates a default subclient that represents all the DB2 MultiNode database partitions on the affected client computers. After, you can create one or more user-defined subclients for the backup set to suit your backup strategy.

Creating a Backup Set

Each DB2 MultiNode backup set is actually an existing DB2 DPF or DB2 pureScale database. After configuring the DB2 MultiNode pseudo-client, you must create at least one DB2 backup set; however, you can create the backup set only if a DB2 database exists in the instance. If there is a DB2 DPF or DB2 pureScale database in that instance, you can create a corresponding backup set with the same name as the database. If not, you cannot create a DB2 backup set. Once you create a DB2 backup set, a default subclient is automatically created.

Once you have discovered the databases, you can create a backup set for each of the discovered database in order to perform backup and restore operations on the database. During DB2 instance discovery, options such as DB2 home path and user account, are preset. When instances are manually added, these options can be customized. Use the following steps to create a new backup set for an existing DB2 DPF or DB2 pureScale database.

  1. From the CommCell Browser, navigate to Client Computers | <DB2 MultiNode Client>.
  2. Right-click the <Instance>, and then click Properties.
  3. On the Instance Properties dialog, check the Auto detect new and deleted partitions check box, and click OK.
  4. From the CommCell Browser, navigate to Client Computers | <DB2 MultiNode Client>.
  5. Right-click the <Instance>, point to All Tasks, and then click Discover Databases.
  6. Right-click the <Instance>, point to All Tasks, and then click Create New Backup Set.
  7. On the Creating New Backup Set dialog box:
    1. Select the Databases under the Available DB Names, and then click the right arrow button to move them into the Selection box.
    2. In the Storage Policy for all Log Files box, select the storage policy name.
    3. Click OK.

Configuring a Backup Set

Use the following steps to configure a backup set:

  1. From the CommCell Browser, navigate to Client Computers | <DB2 MultiNode Client> | <Instance>.
  2. Right-click the desired <BackupSet>, and then click Properties.
  3. On the Instance Properties dialog:
    1. In the Storage Policy for all Log Files box, select the storage policy name.
    2. Check the Connect as Different User check box.
    3. Click Change.
    4. On the DB2 User Account  dialog:
      • In the DB2 User Account box, enter the login credentials to access the DB2 client.
      • In the Password box, enter the password.
      • In the Confirm Password box, re-enter the password, and then click OK.
  4. Click OK.

Changing the Account for Accessing Databases or Applications

You can change the DB2 MultiNode user account for accessing a database to perform backup and restore operations. Use the following steps to change the user account for accessing a database:

  1. From the CommCell Browser, navigate to Client Computers | <DB2 MultiNode Client> | <Instance>.
  2. Right-click the <BackupSet>, and then click Properties.
  3. On the Instance Properties dialog:
    1. In the Storage Policy for all Log Files box, select the storage policy name.
    2. Check the Connect as Different User check box.
    3. Click Change.
    4. On the DB2 User Account  dialog:
      • In the DB2 User Account box, enter the login credentials to access the DB2 client.
      • In the Password box, enter the password.
      • In the Confirm Password box, re-enter the password, and then click OK.
  4. Click OK.

Managing Subclients

The DB2 MultiNode iDataAgent is designed to back up and restore DB2 DPF and DB2 pureScale database partitions, which include the database files along with the associated table spaces, history files and log files. A default subclient is created by the system only after you first create and configure a DB2 MultiNode pseudo-client and instance and then an associated backup set (database) from the CommCell Console. The default subclient that is created for a backup set  includes all the database partitions (nodes) for all the clients that were selected during DB2 MultiNode instance creation. However, you can use the CommCell Console to create user-defined subclients to distribute some of the database content by configuring the subclient. Any content that you do not distribute to the user-defined subclients remains in the default subclient. Because multiple DB2 database partitions can be backed up from the client, you can create multiple backup sets on the client and therefore multiple user-defined subclients for these backup sets.

Before you back up data, you must define the data that you want to back up and how this data should be backed up. This is done by creating one or more subclients for the databases that you are backing up. For the DB2 MultiNode iDataAgent, a subclient defines whether:

  • Entire databases or only a subset of objects within the databases is backed up
  • Data intended for backup will be backed up with the DB2 database online or offline
  • Log files should be included in the database backup for online backups
  • Prebackup or postbackup processes will be run

Depending on your needs, you can create multiple subclients for backing up an entire database, individual table spaces, multiple table spaces, and log files with the database either online or offline.

When creating and configuring subclients for DB2 agents, keep in mind the following considerations:

  • DB2 MultiNode has a configuration requirement to indicate whether the database should be online or offline during backups in addition to specifying the subclient name, content and storage policy association.
  • Logs are used to recover database transactions that have been lost due to an operating system or disk failure. This recovery is done by applying the logs to an online backup. DB2 MultiNode archives log files once they become full. Because of their importance in recovering data, it is suggested that you create separate subclients for backing up log files.   Log backups in a DB2 pureScale configuration require the availability of all clients (log files are unique on each client).
  • DB2 MultiNode subclients include one or more table spaces. As databases are added to the table spaces, the subclients are updated automatically. This process is referred to as an Automatic Subclient Update.

Creating a New Subclient

Each DB2 MultiNode backup set is actually an existing DB2 database. After configuring the DB2 MultiNode pseudo-client, you must create at least one DB2 backup set; however, you can create the backup set only if a DB2 database exists in the instance. If there is a DB2 database in that instance, you can create a corresponding backup set with the same name as the database. If not, you cannot create a DB2 backup set. Once you create a DB2 backup set, a default subclient is automatically created. Use the following procedure to create a new subclient:

  1. From the CommCell Browser, navigate to Client Computers |<DB2 MultiNode Client > | <Instance>.
  2. Right-click the <BackupSet>, Point to All Tasks, and then click New Subclient.
  3. On the Creating New Subclient dialog:
    1. In the Subclient name box, enter the subclient name.
    2. Navigate to the Storage Device tab, enter or select the Storage Policy.
  4. Click OK.

Creating a Subclient for Offline Backups

  1. From the CommCell Browser, navigate to Client Computers |<DB2 MultiNode Client > | <Instance>.
  2. Right-click the <BackupSet>, Point to All Tasks, and then click New Subclient.
  3. On the Creating New Subclient dialog:
    1. In the Subclient name box, enter the subclient name.
    2. Navigate to the Storage Device tab, enter or select the Storage Policy.
    3. Navigate to the Backup Arguments tab, select Offline Backup.
  4. Click OK.

Creating a Subclient for Online Backups

  1. From the CommCell Browser, navigate to Client Computers | <DB2 MultiNode Client> | <Instance>.
  2. Right-click the <BackupSet>, Point to All Tasks, and then click New Subclient.
  3. On the Creating New Subclient dialog box:
    1. In the Subclient name box, enter the subclient name.
    2. Navigate to the Storage Device tab, enter or select the Storage Policy..
    3. Navigate to the Backup Arguments tab, select Online Backup.
  4. Click OK.

Creating a Subclient to Backup Individual Datafiles or Tablespaces

In addition to backing up the entire DB2 database, you can also backup specific tablespaces which undergo frequent changes.

Procedure

  1. From the CommCell Browser, expand Client Computers > client > DB2 MultiNode > Instance.
  2. Right-click the backup_set, point to All Tasks and then click Create Subclient.

    The Create New Subclient dialog box appears.

  3. On the General tab, in the Subclient name box, enter a name for the subclient.
  4. On the Content tab:
    1. Select the Data check box.
    2. Select mode to backup the database in.

      To perform the backup when the database in online, select the Online Database option.

      To perform the backup when the database in offline, select the Offline Database option.

    3. In the database object box, select the datafiles and tablespaces to include in the backup.
  5. On the Storage Device tab, select the data storage policy from  the Data Storage Policy list.
  6. Click OK to close the Create New Subclient dialog box.

Creating a Subclient for Log Backups

  1. From the CommCell Browser, navigate to Client Computers |<DB2 MultiNode Client > | <Instance>.
  2. Right-click the <BackupSet>, point to All Tasks, and then click New Subclient.
  3. On the Creating New Subclient dialog:
    1. In the Subclient name box, enter the subclient name.
    2. Navigate to the Storage Device tab, enter or select the Storage Policy..
    3. Navigate to the Content tab, clear the Backup Data checkbox and check the Backup Log Files check box..
  4. Click OK.

Associating a Subclient to a Storage Policy

You can associate a subclient to a storage policy. use the following steps to associate a subclient to a storage policy:

  1. From the CommCell Browser, navigate to Policies.
  2. Right-click Storage Policies, and then select Subclient Associations.
  1. Select the desired subclient.
  2. In the Change all selected Storage Policies to box, select the desired Storage Policy, and then click Apply.
  3. Click OK.

Configuring User Accounts for Backups

The DB2 iDataAgent requires a user account that has sufficient privileges to perform the following operations:

  • Perform backup and restore operations
  • Stop and start DB2 services on Windows and UNIX clients

By default, backup and restore operations use the DB2 administrator account. You can use a a DB2 non-administrator account. The account must have the following privileges:

Operating System Required Privileges
Windows Local Administrator of the computer on where the DB2 database resides
UNIX Member of the user group that was assigned when the DB2 Agent was installed
All
  • Member of the SYSMAINT_GROUP and SYSCTRL_GROUP authorities.

    db2 update dbm cfg using SYSMAINT_GROUP <user_name or user_group>
    db2 update dbm cfg using SYSCTRL_GROUP <user_name or user_group>

  • Database administrator (DBADM) privileges on the database.

    db2 grant dbadm on database to <new_user>

At the Client Computer Group Level

This user account will be used for all computers within a Client Computer Group. Configure the user account at this level if different users will be conducting backup and restore operations for each Client Computer Group in your organization. This user account will override the user account configured at the CommCell level.

  1. From the CommCell Browser, navigate to the Client Computer Groups node.
  2. Verify that all the Agent clients for which you wish to configure the user account are included in the Client Computer Groups.
  3. Right-click the <Client Group> and click Properties.
  4. On the Client Group dialog:
    1. Navigate to the Advanced Settings tab.
    2. Check the Override higher levels settings check box.
    3. Select one of the following:
      • Use Local System Account, if the computer's Administrator account contains the required privileges.
      • Impersonate User, to use a different account that contains the required privileges. Enter the User Name and Password for this account in the space provided.
    4. Click OK.

At the Instance Level

This user account will be used for subsequent new backup sets created within the instance. Configure the user account at this level if backup and restore operations will be conducted by a different user for each instance.

  1. Navigate to Client Computers | <DB2 MultiNode Client>.
  2. Right-click the <Instance> and then click Properties.
  3. On the Instance Properties dialog:
    1. Check the Connect as Different User check box.
    2. Click Change.
    3. On the DB2 User Account  dialog:
      • In the DB2 User Account box, enter the login credentials to access the DB2 client.
      • In the Password box, enter the password.
      • In the Confirm Password box, re-enter the password, and then click OK.
  4. Click OK.

At the Backup Set Level

This user account will be used for a specific backup set. When you modify the user account for an instance, new backup sets created within the instance use the new account. However, existing backup sets continue to use the earlier user account unless modified manually.

Use the following steps to change the user account for a specific backup set:

  1. Navigate to Client Computers | <DB2 MultiNode Client> | <Instance>.
  2. Right-click the <backup set>, and click Properties.
  3. On the Backup Set Properties dialog:
    1. Check the Connect as Different User check box.
    2. Click Change.
    3. On the DB2 User Account  dialog:
      • In the DB2 User Account box, enter the login credentials to access the DB2 client.
      • In the Password box, enter the password.
      • In the Confirm Password box, re-enter the password, and then click OK.
  4. Click OK.

Enabling Database Configuration Parameters

Each DB2 database has its own configuration. To successfully back up DB2 data  in some cases, you must enable the appropriate database configuration parameters. Set these parameters based on the state of the database, backup type, and/or data type as follows:

Before you change any configuration parameter, ensure that no applications are currently using the affected database. Also, be sure to consult your database administrator regarding business requirements for the database.

Backups in General

To back up any type of DB2 data online or offline, update the LOGARCHOPT1, LOGARCHMETH2 and VENDOROPT database configuration parameters by entering the following commands:

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>'"

Delta or Incremental Backups

Enable the TRACKMOD database configuration parameter to perform the delta or incremental DB2 backups. From the DB2 Console, enter the following command to set the TRACKMOD parameter:

For DB2 DPF

db2 update database configuration for <database name> DBPARTITIONNUM (n)using TRACKMOD on

For DB2 pureScale

db2 update database configuration for <database name> using TRACKMOD on

Whenever you change the TRACKMOD database configuration parameter, be sure to run a full offline database backup. Otherwise, the TRACKMOD parameter will not take effect.

Log Backups and Archives

With the SBT interface, log files are staged to an archive path, and an On Demand backup of the log files is performed when a certain threshold is reached. Alternatively, the user can submit a backup request for any number of log files from the CommCell Console. The USEREXIT/SBT interface program takes the logs from the DB2 directory and transfers them first to the threshold directory that was defined during the DB2 iDataAgent install, and then to tape. If you subsequently use the Delete option, the logs are deleted from the threshold directory; otherwise, the logs are kept in this directory. By default, the threshold directory can hold 1000 logs. If the threshold directory attempts to hold more than 1000 logs, a command line backup for the logs starts automatically, and the logs are transferred to tape. Control the threshold value by adding the sDb2ThresholdALFN <number> additional setting to the DB2Agent, where <number> indicates the number of logs y to hold in the threshold directory before the logs will automatically start backing up to tape. Otherwise, by default, the threshold directory can hold 1000 logs.

Note: if sDb2ThresholdALFN is set to 1, in this case the DB2 archive log will be backed up directly to tape instead of moving to the staging archive directory before moving to tape.  We recommend setting the value to 25 for optimal use of resources.

In order to use the DB2 database configurations for archive log backups, ensure that the LOGARCHMETH1/USEREXIT parameter is set.

NOTE: USEREXIT and LOGRETAIN are deprecated in Version 9.5 and higher but are still being used by pre-Version 9.5 data servers.

Use the following steps to enable archive log backups:

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/simpana/Base/libDb2Sbt.so'"

For DB2 pureScale with LOGARCHMETH1

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

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

Enabling Log Deletion after Backup

Once you backup the archive logs, you can choose to delete the archived log files from the archive log path defined during the iDataAgent install.

Use the following steps to enable archive log deletion after a log backup:

  1. From the CommCell Browser, navigate to Client Computers |< DB2 MultiNode Client > |  <Instance>.
  2. Right-click the <BackupSet>, point to All Tasks, and then click New Subclient.
  3. On the Creating New Subclient dialog:
    1. In the Subclient name box, enter the subclient name.
    2. Navigate to the Storage Device tab, enter or select the Storage Policy.
    3. Navigate to the Content tab, clear the Backup Data checkbox and check the Backup Log Files and Delete Log Files After check boxes..
  4. Click OK

Modifying the Threshold Value for Log Backups

By default, the archive log path given at the time of installation holds 1000 archive logs. Once the archive logs reach this threshold value, automated log backup gets started.

Use the following steps to change the threshold value to start an automated log backup:

  1. From the CommCell Browser, navigate to Client Computers.
  2. Right-click <DB2 MultiNode Client> and then click Properties.
  3. On the Advanced Client Properties dialog, navigate to the Additional Settings tab and click Add.
  4. On the Add Additional Settings on Unix Client dialog:
    1. In the Name field, enter sDb2ThresholdALFN.
    2. Click Lookup.  The Add Additional Settings on Unix Client dialog box will automatically display the Category, Type and Value of this additional setting.
    3. Set the Value

      Set the value to 1 if you want the logs to be backed up immediately. When doing this, make sure that there are no log backups configured from the CommCell Console.

  5. Click OK.

Modifying the Archive Path

Once the DB2 online log files are full, they are moved to DB2 Archive folder. By default, at the time of installation of DB2 iDataAgent, a single parent location is specified for storing Archive files, Audit Error logs and files that are used in DB2 recovery process. However, if you want, you can change the Archive path after the installation of DB2 iDataAgent.

Note: In a multi-instance and multi-database configuration, you can configure multiple archive paths by configuring this additional setting for each instance and database.

  1. From the CommCell Browser, right-click the client, and then click Properties:
  2. In the Client Properties dialog box, click the Additional Settings tab and then click Add.
  3. In the Add Additional Settings dialog box, enter the details for the additional setting:
    1. Set the path.
      • To set the archive path when there is one database in the configuration, in the Name box, type sDB2_ARCHIVE_PATH.
      • To set the archive path in a multi-instance and multi-database configuration, in the Name box, type <db2 instance name>_<db name>_sDB2_ARCHIVE_PATH.

        Note: The DB2 instance name (db2_instance_name) and the DB2 database name (db_name) must be in upper case.

    2. In Category box, select Db2Agent.
    3. In the Type box, select String.
    4. In the Value box, type <software_install_directory>\archive_path.
    5. Click OK to close the Add Additional Settings dialog box.
  4. Click OK to close the Client Properties dialog box.

Modifying the Audit Error Path

By default, at the time of installation of DB2 iDataAgent, a single parent location is specified for storing Audit Error logs, Archive files and files that are used in DB2 recovery process. However, if you want, you can change the Audit Error path after the installation of DB2 iDataAgent.

Note: In a multi-instance and multi-database configuration, you can configure multiple archive paths by configuring this additional setting for each instance and database.

  1. From the CommCell Browser, right-click the client, and then click Properties:
  2. In the Client Properties dialog box, click the Additional Settings tab and then click Add.
  3. In the Add Additional Settings dialog box, enter the details for the additional setting:
    1. Set the path.
      • To set the audit error path when there is one database in the configuration, in the Name box, type sDB2_AUDIT_ERROR_PATH.
      • To set the audit error path in a multi-instance and multiple database configuration, in the Name box, type <db2 instance name>_<db name>_sDB2_AUDIT_ERROR_PATH.

        Note: The DB2 instance name (db2_instance_name) and the DB2 database name (db_name) must be in upper case.

    2. In Category box, select Db2Agent.
    3. In the Type box, select String.
    4. In the Value box, type <software_install_directory>\audit_path.
    5. Click OK to close the Add Additional Settings dialog box.
  4. Click OK to close the Client Properties dialog box.

Modifying the Retrieve Path

Retrieve path is the location where the files that are required for DB2 recovery process are stored. By default, at the time of installation of DB2 iDataAgent, a single parent location is specified for storing the files the are used in DB2 recovery process, Audit Error logs and Archive files. However, if you want, you can change the Retrieve path after the installation of DB2 iDataAgent. Use the following steps for modifying the path to the Retrieve folder:

Note: In a multi-instance and multi-database configuration, you can configure multiple archive paths by configuring this additional setting for each instance and database.

  1. From the CommCell Browser, right-click the client, and then click Properties:
  2. In the Client Properties dialog box, click the Additional Settings tab and then click Add.
  3. In the Add Additional Settings dialog box, enter the details for the additional setting:
    1. Set the path.
      • To set the retrieve path when there is one database in the configuration, in the Name box, type sDB2_RETRIEVE_PATH.
      • To set the retrieve path in a multi-instance and multiple database configuration,  in the Name box, type <db2 instance name>_<db name>_sDB2_RETRIEVE_PATH.

        Note: The DB2 instance name (db2_instance_name) and the DB2 database name (db_name) must be in upper case.

    2. In Category box, select Db2Agent.
    3. In the Type box, select String.
    4. In the Value box, type <software_install_directory>\retrieve_path.
    5. Click OK to close the Add Additional Settings dialog box.
  4. Click OK to close the Client Properties dialog box.

Modifying Backup Performance

Several options are available for enhancing backup performance and reducing the network bandwidth used for  backups. These are DB2 database configuration options that are set via the SnapProtect software.  They are dependent on the DB2 hardware and configuration.  Refer to your DB2 documentation for information on how to set these options.These options include:

  • Specifying the buffer size for the backups. When you are backing up the database to multiple locations, you can give sufficient buffer value to improve performance.

  • Specifying the size of the buffer.

  • Setting the parallelism. If the DB2 database contains large number of tablespaces and indexes, you can perform a backup operation faster when you set maximum number of concurrent parallelism queries to take advantage of available Input/Output bandwidth and processor power of DB2 server. DB2's query parallelism targets Input/Output intensive queries (ie., tablespace scans, large index scans etc.) and CPU intensive queries (i.e.., joins, sorts, complex expressions etc.). If the number is not set, optimal value will be chosen automatically.

DB2 iDataAgents run backups using a system-generated script that is run behind the scenes from a command line. The CommCell Console serves as a front-end user interface for specifying various backup arguments and parameters that are passed to the backup script that is run. Use the following steps to configure backup arguments:

  1. From the CommCell Browser, navigate to Client Computers |< DB2 MultiNode Client > | <Instance> | <BackupSet>.
  2. Right-click the <Subclient>, and then click Properties.
  3. On the Subclient Properties dialog:
    1. Navigate to the Backup Arguments tab.
    2. In the Number of Buffers box, enter or select the number of buffers.  The default is 1.
    3. In the Buffer Size box, type or select the Buffer Size.  The minimum value is 8, and the default value is 1024.
    4. In the Parallelism box, enter or select the number of Parallelism queries you want to set for your backup operation. 

      If the number is not set, the optimal value is automatically  chosen.

  4. Click OK.

Enabling DB2 Compression

You can use DB2 compression method to compress backup data. Use the following steps to enable DB2 compression method on the backup data:

  1. From the CommCell Browser, navigate to Client Computers | <DB2MultiNode Client> | <Instance> | <BackupSet>.
  2. Right-click the <Subclient>, and then click Properties.
  3. On the Subclient Properties dialog:
    1. Navigate to the Backup Arguments tab.
    2. Check the Use DB2 Compression check box.
    3. In the Buffer Size box, enter or select the Buffer Size.  The minimum value is 8, and the default value is 1024.
    4. In the Parallelism box, enter or select the number of Parallelism queries you want to set for your backup operation. 
  4. Click OK.

Configuring the Number of Days to Hold Media Log Offset Files

By default, media log offset files older than 4 days are removed from the aAUDIT_ERROR_PATH directory.  This can be configured to a different number

  1. From the CommCell Browser, navigate to Client Computers.
  2. Right-click <Client>, and then click Properties.
  3. On the Client Properties dialog box, click Advanced.
  4.  On the Advanced Client Properties dialog box, navigate to the Additional Settings tab.
    1. Click Add.
    2. In the Name box, type nDB2PruneMediaOffsetFileAfterDays. The Category and Type details will be automatically displayed.
    3. In the Value box, enter the number of days to hold the media log offset files.
    4. Click OK.
  5. Click OK.

Configuring Streams for Backups

You can specify the number of streams that can be used for backup operations. By default, backup data is sent to media in two streams. This means that a database is sent to media during a backup in two parallel waves. This results in backup taking about half the time to complete as it otherwise would if only one stream is used.

You can increase the number of streams used for backups for a particular subclient provided the number of streams does not exceed the maximum number configured in the subclient's storage policy. Increasing the number of streams for a subclient further reduces the amount of time a backup takes to complete. For example, increasing the number of streams from 2 to 3 enhances backup time from one-half that of a single stream to one-third. Keep in mind that the same number of streams used for performing a backup will be needed to restore the data Use the following steps to configure streams for backups:

  1. From the CommCell Browser, navigate to Client Computers | < DB2MultiNode Client> | <Instance> | <BackupSet>.
  2. Right-click the <Subclient>, and then click Properties.
  3. On the Subclient Properties dialog:
    1. Navigate to the Storage Device tab.
    2. In the Stream column of Number of Data Backup Streams box, double-click and enter the number of backup streams.
  4. Click OK.

Configuring Streams for Best Case Reservation

Multiple streams are supported for data protection and recovery operations from DB2 MultiNode nodes. You can perform a successful data backups even if the number of device streams configured in the nodes is more than the streams configured for a storage policy.

Use the following steps to configure streams for backups:

  1. From the CommCell Browser, navigate to Client Computers | < DB2 MultiNode Client>| <Instance> | <BackupSet>.
  2. Right-click the <Subclient>, and then click Properties.
  3. On the Subclient Properties dialog:
    1. Navigate to the Storage Device tab.
    2. In the Stream column of Number of Data Backup Streams box, double-click and enter the number of backup streams.  In this case, the number of streams for a node cannot be a 0 (zero).
  4. Click OK.

Configuring Multiple Data Paths for Load Sharing

In a primary copy, you can now allow multiple streams of a backup job to share the load on multiple DataPaths. This will release the load on a single Data Path and allows you to obtain the streams from Multiple Data Paths. You can configure a storage policy primary copy with multiple data paths to perform parallel backups.

For Example:

If you need to backup simultaneously to 8 drives of two or more libraries as part of one backup job, then you must configure the following to perform parallel backups using the resources that are allocated on all the drives that were part of different data paths in a library:

  • Configure a storage policy primary copy with multiple data paths
  • Reserve resource allocation for these data paths using media management's Resource Manager.

This allows you to allocate multiple streams of a backup job to share the load on multiple Data Paths.

Configuring a Primary Copy with Multiple Data Paths

Use the following steps to configure a primary copy with multiple data paths:

  1. From the CommCell Browser, navigate to Policies  | Storage Policies.
  2. Select the Storage Policy that you are using for your iDataAgent. Select the Primary Copy. If you have not yet created a Primary Copy for your iDataAgent, see Creating a Storage Polocy for a step-by-step procedure to create a primary copy.
  3. Right click the Primary Copy and click Properties.
  4. Click the Data Paths tab.
  5. Click Add to select and add the additional data paths.

  6. Click OK.

    In the following image, you can view 2 different libraries (For example, HP EML E Series 28 and HP MSL G3 Series 29) configured as different DataPaths.

    DataPathId="111" MediaAgent="dbcs" Library="HP EML E Series 28" DrivePool="DrivePool(dbcs)32" SpareGroup="Default Scratch“

    DataPathId="112" MediaAgent="dbserve12" Library="HP EML E Series 28" DrivePool="DrivePool(dbserve12)28" SpareGroup="Default Scratch"

    DataPathId="113" MediaAgent="dbcs" Library="HP MSL G3 Series 29" DrivePool="DrivePool(dbcs)33" SpareGroup="Default Scratch"

    DataPathId="114" MediaAgent="dbserve12" Library="HP MSL G3 Series 29" DrivePool="DrivePool(dbserve12)29" SpareGroup="Default Scratch"

Configuring Resource Manager to Reserve Resource Allocation for Multiple Data Paths

You can create reservations on multiple data paths at the same time if there is not enough Resources from any single data path. Use the following steps to reserve resource allocation using Media Management's Resource Manager for multiple data paths:

  1. From the CommCell Console toolbar, click Control Panel.

  2. Click Media Management.

  3. Click Resource Manager Configuration tab.

  4. Select Allow load-balance on multiple data paths within one backup job. Double click the value box and set the Value as 1.

  5. Click OK.

This will allow the backup job to enforce reservations on multiple datapaths at the same time if the resources are limited from any single datapath.

Determining an Instance Type

When a DB2 MultiNode instance is created, the SnapProtect software detects the database type and sets the appropriate values (DB2 DPF or DB2 pureScale)

After creating an instance you can view the  DB2 Instance Type on the Instance Properties dialog.

  1. From the CommCell Browser, navigate to Client Computers | <DB2 MultiNode Client>.
  2. Right-click the <Instance>, and then click Properties.  The DB2 Instance Type indicates DPF or pureScale.

Modifying an Agent, an Instance, a Backup Set or a Subclient

There are several configurable properties available for your agent that can be modified from the agent, instance, or subclient level as per need.

It is recommended that that you do not modify the properties of a subclient when a job is in progress for that specific subclient. If a job is in progress, either wait for the job to complete or kill the job from the Job Controller.

The following table describes the properties that can configured from the agent, instance, and subclient levels.

Option Description Related Topics
Change Storage Policies You can modify the storage policies in any of the following situations:
  • To include a different media for the backup operation.
  • To use a storage policy with a different retention criteria.

You can change the storage policies from the subclient level.

  1. From the CommCell Browser, right-click the subclient.
  2. Click Properties.
  3. Click Storage Device.
  4. Select the Storage policy from the drop-down menu.
  5. Click OK.
Refer to Storage Policies.
Rename a Subclient

You can rename a subclient:

  1. From the CommCell Browser, right-click the subclient.
  2. Click Properties.
  3. Type the new name in the  Subclient name field.
  4. Click OK.
 
Rename an Instance You can rename a subclient.
  1. From the CommCell Browser, navigate to Client Computers | <DB2 MultiNode Client>.
  2. Right-click the <Instance>, and then click Properties
  3. In the Instance box, enter the instance name.
  4. Click OK.
 
Data Transfer Options You can configure the available resources for transferring data secured by data protection operations from the subclient level. This includes the following:
  • Enable or disable Data Compression either on the client or on the MediaAgent.
  • Configure the transfer of data in the network using the options for Network Bandwidth Throttling and Network Agents.

You can configure the data transfer options.

  1. From the CommCell Browser, right-click the subclient.
  2. Click Properties.
  3. Click Storage Device.
  4. Click Data Transfer Option tab.
  5. Choose the appropriate software compression option for this subclient.
  6. Select Throttle Network Bandwidth and set the required bandwidth.
  7. Click OK.
Refer to Data Compression and Network Bandwidth Throttling.
View Data Paths You can view the data paths associated with the primary storage policy copy of the selected storage policy or incremental storage policy. You can also modify the data paths including their priority from the subclient level.
  1. From the CommCell browser, right-click the subclient.
  2. Click Properties.
  3. Click Storage Device.
  4. Select Storage Policy from the drop-down menu.
  5. Click Data Paths.
 
Configure a Subclient for Pre and Post Processing of Data Protection You can add, modify or view Pre/Post processes for the subclient. These are batch files or shell scripts that you can run before or after certain job phases.
  1. From the CommCell browser, right-click the subclient.
  2. Click Properties.
  3. Click Pre/Post Process.
  4. Click one of the following phases and enter the full path of the process that you want to execute during that phase. Alternatively, click Browse to locate the process (applicable only for paths that do not contain any spaces).
    • PreBackup Process
    • PostBackup Process
    • PreSnap Process
    • PostSnap Process
  5. Click OK.
  6. Select Run Post Backup Process for all attempts to run a post backup process for all attempts.
  7. For subclients on Windows platforms, Run As displays Not Selected.

    If you want to change the account that has permission to run these commands, click Change.

    1. In the User Account dialog box, select Use Local System Account, or select Impersonate User and enter the user name and password. click OK.
    2. If you selected Local System Account, click OK to the message advising you that commands using this account have rights to access all data on the client computer.
Refer to Pre/Post Processes.
Configure Activity Control You can enable backup and restore operations from the agent and subclient level. However, you can enable restore operations only from the agent level.
  1. From the CommCell browser, right-click the subclient.
  2. Click Properties.
  3. Click Activity Control, select or clear option(s) as desired.
  4. Click OK.
Refer to Activity Control.
Configure User Security You can configure user security from the agent or subclient level.

You can perform the following functions:

  • Identify the user groups to which this CommCell object is associated.
  • Associate this object with a user group.
  • Disassociate this object from a user group.
  1. From the CommCell browser, right-click the subclient.
  2. Click Properties.
  3. Click Security.
  4. Select the appropriate user groups to which you want to associate to the CommCell object from the Available Groups pane, and then move the user group to the Associated Groups pane.
  5. Click OK.
Refer to User Administration and Security.
Enable and Disable Data Encryption When you configure encryption at the client level, it is configured automatically for all the subclients associated with all the agents installed on that client. If you want to disable or change the encryption at the subclient level, follow the steps given below:
  1. From the CommCell browser, right-click the subclient.
  2. Click Properties.
  3. Click Encryption.
  4. Select the desired encryption.
  5. Click OK.
Refer to Data Encryption.
View Software Version and Installed Updates At the client level, the Version tab of the Properties dialog box displays the software version of the component.
  1. From the CommCell Browser, expand Client Computers.
  2. Right-click the appropriate client, and then click Properties.
  3. Select the Version tab.
  4. Click OK.
 
CommCell Configuration Report The CommCell Configuration Report provides the properties of the CommServe, MediaAgents, clients, agents, subclients, and storage policies within the CommCell based on the selected filter criteria.
  1. From the CommCell browser, click Reports icon.
  2. Select CommCell Configuration.
  3. Click Run.
Refer to CommCell Configuration.

Deleting an Agent, an Instance, a Backup Set or a Subclient

The following sections describe the steps involved in deleting an agent, instance, or subclient.

When you delete an instance or backupset, the associated data is logically deleted and you can no longer access the corresponding data from CommCell Console for recovery purposes.

Refer to the troubleshooting article on Recovering Data Associated with Deleted Clients and Storage Policies for information on how to recover data if you accidentally delete an entity.

Deleting an Agent

You need to uninstall or DeConfigure the agent software from the client computer before deleting from CommCell Browser. After you delete the client software, you can either leave the corresponding data intact for appropriate action or you can remove the data immediately. If you choose to remove the data immediately, you must delete the agent from the CommCell Browser. If you delete the agent, all of the agent's data is irretrievably lost.

  • You cannot delete an agent while operations for that agent are running.
  1. From the CommCell Browser, navigate to Client Computers | <Client>.
  2. Right-click the <Agent>, and then click Delete.
  3. A confirmation message is displayed with the following message:

    This operation will permanently delete the data backed up from this level and it cannot be restored.

  4. Click OK to continue with the deletion operation or click No to abort the deletion.

Deleting an Instance

Consider the following before deleting an instance:

  • When you delete a specific instance all job schedules and job histories that pertain to any of the levels within the deleted instance are deleted.
  • You cannot delete an instance if it is being backed up. Attempts to delete an instance under such conditions cause the deletion to fail. If a backup is in progress, either wait for the backup to complete or kill the backup job using the Job Manager. Once the backup is no longer in progress, you can delete the instance level.
  • You cannot delete an instance if there is only one instance present for an agent. To delete the final instance, you must remove the agent software from the client computer.
  1. From the CommCell Browser, right-click the instance that you want to delete, click All Tasks and then click Delete.
  2. click Yes to confirm the deletion. (clicking No cancels the deletion and retains the node.)
  3. Enter the requested phrase in the Enter Confirmation Text dialog box and click OK. This should delete the instance.

Deleting a Backup Set

Consider the following before deleting a subclient:

  • Schedules associated with the subclient are also automatically deleted.
  1. From the CommCell Browser, navigate to Client Computers | <DB2 MultiNode Client> | <Agent> | <Instance>.
  2. Right-click the <BackupSet > that you want to delete, and then click Delete.
  3. A confirmation message is displayed, asking if you want to delete the subclient.

    Click No to cancel the deletion and retain the subclient, or click Yes to continue the deletion.

Deleting a Subclient

In cases where a new subclient is created with the same name as a deleted subclient, the system will append a Unix time stamp to the deleted subclient's name in data protection job history reports and views to distinguish the two subclients. For example, subclientname_1104257351.

Consider the following before deleting a subclient:

  • You cannot delete a default subclient.
  • Schedules associated with the subclient are also automatically deleted.
  1. From the CommCell Browser, navigate to Client Computers | <DB2 MultiNode Client> | <Agent> | <Instance> | < BackupSet >.
  2. Right-click the <Subclient> that you want to delete, and then click Delete.
  3. A confirmation message is displayed, asking if you want to delete the subclient.

    Click No to cancel the deletion and retain the subclient, or click Yes to continue the deletion.