Creating a DB2 Subclient for Table Level Restores

You can create a subclient for a restore of one or more database tables. You can restore the tables without affecting other database objects.

Best Practice: To ensure that a point-in-time restore is successful, select the Online Database option (Content tab).

Before You Begin

Configure a backup set for the DB2 database.

Procedure

1. From the CommCell Browser, expand Client Computers > client > DB2 > Instance.

2. Right-click the backup_set, point to All Tasks, and then click Create Subclient.

   The Create New Subclient dialog box appears.

3. In the General tab, in the Subclient name box, enter a name for the subclient.

4. On the Content tab:

   • Select the Data check box.

   • Select the 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.

   • Clear the Online Subset check box.

   • Optional: To exclude the DB2 log files from the online backup image on a DB2 version that is 9.7 or later, select the Exclude Logs from Backup Image check box.

5. On the Storage Device tab from the Data Storage Policy list, select the storage policy that the software uses for data backups.

6. On the Advanced Options tab, select the Backup Log Files check box when you choose the Online Database option.

7. On the Advanced Options tab, select the options for this subclient.

   1. Select the Enable Table Browse check box to allow table level restores.

   2. Optional: When you choose the option to back up the database (the Online Subset option), select the backup log options.

      Option	Description
      Delete Log Files After check box	Delete the logs after the backup. This deletes the logs from the archive log path. You can optionally delete the logs after a specified time period.
      Disable Switch Current Log check box	Disable the log switch. When the switch is on, the current redo log file is closed (even if it is not filled up completely) and the next redo log file is used for writing using a log switch. The closed redo log file is then archived during the log phase.

8. Optional: Select the subclient options.

   Run scripts before or after the backup

   You can choose to run the post-process script even if the backup job failed.

   To pass the database instance name to the script, see Passing the Instance Name to Pre and Post Scripts for Databases.

   On the Pre/Post Process tab:

   1. In the PreBackup Process box, type the full path name for the script.

   2. In the PostBackup Process box, type the full path name for the script.

   3. To run the post backup process regardless of the job's outcome, select the Run Post Process for all attempts check box.

   Use compression to optimize backup storage

   On the Advanced Options tab, select the Use Db2 compression check box.

   When you select this option, the Commvault software applies the DB2 compression feature to all the backups for this subclient.

   Fore more information about DB2 compression, go to the DB2 website, compression and storage.

   Use DB2 DEDUP DEVICE

   When this is enabled, the DB2 deduplication parameter DEDUP_DEVICE is used. This feature is available starting on DB2 version 9.7 with FixPack 3.

   For additional information about the DB2 DEDUP_DEVICE parameter, go to the DB2 Knowledge Center, DEDUP_DEVICE.

   On the Advanced Options tab, select the Use Dedupe Device check box.

9. Click OK to close the Create New Subclient dialog box.

After you have the backup image, you can use the DB2 backup check command (db2chkbkp) command to verify that you can restore the backup image. For additional information, go to the DB2 Knowledge Center, db2chkbkp.

What to Do Next

Perform a backup

After you configure your subclient for table level restores, the next scheduled backup on the subclient is converted to a full backup.