Loading...

Advanced Restore - DB2 MultiNode Agent

Table of Contents

Restore Considerations for a DB2 pureScale Configuration

In a DB2 pureScale environment, the following needs to be taken into account before performing a restore.

For a data only restore, only one node needs to be available. The default node that is chosen is the last one that the software used for a backup or restore. To see see which one is used by default:

  1. From the CommCell Browser, navigate to Client Computers > client > DB2 MultiNode > instance.
  2. Right-click the backup_set.
  3. The Catalog Partition No. on the Properties dialog box displays the node.

To change the node priority.

  1. From the CommCell Browser, navigate to Client Computers > client > DB2 MultiNode > instance > backup_set.
  2. Right-click the subclient  and click Properties.
  3. On the Properties dialog box, navigate to the Data Storage Policy tab under the Storage Device tab.
    1. In the box, select the row corresponding to the node that the software should try first and click the up arrow button.
    2. Click OK.

All nodes must be available for a data and log restore, or a log restore require, because each node maintains its own transaction log.

Restoring and Recovering an Entire Database

You can restore an entire database after you deactivate the affected database. When you deactivate the database, all the db2 non administrative users will be disconnected. The system will automatically activate the database after the restore operation. However, you need to connect the non administrative users manually after the restore operation.

  1. From the CommCell Browser, navigate to Client Computers > client > DB2 MultiNode > instance.
  2. Right-click the backup_set, point to All Tasks and then click Browse and Restore.

    The Browse and Restore dialog box is displayed.

  3. On the Time Range tab, select Latest Backup and click View Content.
  4. Select the databases to restore and click Recover All Selected.

    The Restore Options dialog box is displayed.

  5. On the Recover Database tab, select the Restore Data check box and select the Entire Database option.
  6. Click OK to close the Restore Options dialog box.

Restoring Individual Tablespaces

By default, the DB2 database will be in Offline mode. However, you need to set the database in online mode to restore the individual tablespaces.

  1. From the CommCell Browser, navigate to Client Computers > client > DB2 MultiNode > instance.
  2. Right-click the backup_set, point to All Tasks and then click Browse and Restore.

    The Browse and Restore dialog box is displayed.

  3. On the Time Range tab, select Latest Backup and click View Content.
  4. Select the databases to restore and click Recover All Selected.

    The Restore Options dialog box is displayed.

  5. On the General tab, do the following:
    1. Select the Restore Data check box and select the Database Subset option.
    2. Select the tablespaces from the Latest Database View list.
  6. On the Restore Arguments tab, do the following:
    1. Select the Online or Offline Restore option.
    2. Select an appropriate Backup Image.
  7. Click OK to close the Restore Options dialog box.

Restoring History Files

By default, the DB2 database will be in Offline mode. However, you need to set the database in online mode to restore the history files. You cannot restore history files which contain database records regarding recovery and administration events along with the log files. Hence, make sure to disable the restoring of log files and reapplying the logs (roll-forward) on restored database.

  1. From the CommCell Browser, navigate to Client Computers > client > DB2 MultiNode > instance.
  2. Right-click the backup_set, point to All Tasks and then click Browse and Restore.

    The Browse and Restore dialog box is displayed.

  3. On the Time Range tab, select Latest Backup and click View Content.
  4. Select the databases to restore and click Recover All Selected.

    The Restore Options dialog box is displayed.

  5. On the General tab, select the Restore Data check box and select the History Files option.
  6. Click Advanced.

    The Advanced Restore Options dialog box is displayed.

  7. On the Roll-Forward tab, clear the Roll-forward check box.
  8. On the Log Files tab, clear the Restore Log Files check box.
  9. Click OK to close the Advanced Restore Options dialog box.
  10. Click OK to close the Restore Options dialog box.

Recovering a Database

By default, you can recover the database along with the restore operation. However, you cannot recover a partial database. Also, you will not be able to recover a database while performing an out-of-place restore operation. If you are trying to recover the database using the backup image, you will not be able to reapply the logs for restore.

  1. From the CommCell Browser, navigate to Client Computers > client > DB2 MultiNode > instance.
  2. Right-click the backup_set, point to All Tasks and then click Browse and Restore.

    The Browse and Restore dialog box is displayed.

  3. On the Time Range tab, select Latest Backup and click View Content.
  4. Select the databases to restore and click Recover All Selected.

    The Restore Options dialog box is displayed.

  5. On the Recover tab, select the Recover DB check box.
  6. Select the recover option.
    Expand All

    Recover to the end of the logs

    1. Select the To the End of the logs option
    2. Click Advanced.

      The Advanced Restore Options dialog box is displayed.

    3. On the Roll-Forward tab, select the To the End of the logs check box.
    4. Click OK to close the Advanced Restore Options dialog box.

    Select the All Log Files option.

    Recover to a point-in-time

    Select By Point in Time and enter the Start and End time in the boxes.
  7. Optional: Use a history path.

    The software checks the history file for the backup image to restore. If the history file is not available, restore the history file before you recover the database. If the software does not find all of the information that it needs in the history file path, it looks in the overflow directory. Use this overflow directory path only if you moved log files to a location other than the directory specified by the logpath database configuration parameter.

    1. Select the History File Path check box.
    2. Enter the full path to the history file in the box
    3. Enter the full path to the overflow directory in the Overflow Directory box.
  8. Optional: Run scripts before or after the restore.

    Enter the full path for the pre-recovery and post-recovery script.

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

    1. Click Advanced.

      The Advanced Restore Options dialog box is displayed.

    2. On the Pre/Post tab:

      • In the Pre-Recovery Command box, type the full path name for the script.
      • In the Post-Recovery Command box, type the full path name for the script.
      • To run the post recovery process regardless of the job's outcome, select the Run Post Process for all attempts check box.
    3. Click OK to close the Advanced Restore Options dialog box.
  9. Click OK to close the Restore Options dialog box and start the restore.

Restoring the Backup Images

You can perform a restore from a backup image when you want to perform a scheduled out-of-place restore.

Restoring Backup Images

Use the following steps to restore the backup images in an offline state:

  1. From the CommCell Browser, navigate to Client Computers | <DB2 MultiNode Client> | <Instance>.
  2. Right-click the <Backup_Set>, point to All Tasks and then click Browse and Restore.
  3. On the Browse and Restore dialog box, select Latest Backup and click View Content.
  4. Select the database and click Recover All Selected.

    The Restore Options dialog box appears.

  5. On the Recover Database tab, clear the Recover DB check box.
  6. On the Restore Arguments tab.
    1. Select the database mode for the restore.

      To restore when the database is offline, select the Offline Restore option.

      To restore when the database is online, select the Online Restore option.

    2. Select the backup images from Available Images and click >. The backup images are moved to the Selection box.

      Note: When you select the Use Latest Backup image option, the latest backup image is used for the restore.

  7. Click OK.

Incremental Restores from One Full Backup Image

Use the following steps to perform an incremental restore from one full backup image:

  1. From the CommCell Browser, navigate to Client Computers | <DB2 MultiNode Client> | <Instance>.
  1. Right-click the <Backup_Set>, point to All Tasks and then click Browse and Restore.
  2. On the Browse and Restore dialog box, select Latest Backup and click View Content.
  3. Select the database and click Recover All Selected.

    The Restore Options dialog box appears.

  4. On the Recover Database tab, clear the Recover DB check box.
  5. On the Restore Arguments tab.
    1. Select the Offline Restore check box.
    2. Select the backup images from Available Images and click >. The backup images are moved to the Selection box.
    3. Select Incremental Restore (from one Full backup image) check box.
  6. Click OK.

Using Buffers

Use the following steps to restore the backup images using buffers:

  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 Browse and Restore.
  3. Click View Content on the Browse and Restore Options dialog.
  4. In the right pane of the Browse window, select the databases to restore and click Recover All Selected.
  5. On the DB2 Restore Options dialog box:
    1. On the Recover Database tab, select the Recover DB check box.
    2. On the Restore Arguments tab and select the Online Restore option.
    3. Select the image in the Available Images box and click the > button.
    4. Adjust the Buffer Size as needed.
  6. Click OK.

Restoring to Disk (App Free Restore)

You can restore the backup images of data and logs or multiple backup jobs at a time directly to a location on a disk using CommCell console without the intervention of DB2 application. This is useful for restoring multiplexed data on the same media. The data from different backup jobs are passed back to the client so that all of the interleaved backup jobs can be restored in parallel. You can restore the data associated with a specific backup job such as full, in parallel streams. You can also submit multiple restore jobs from full and incremental backups. Later, you can restore db2 database from db2 command line using backup image from Disk without using the load SnapProtect library.

Use the following steps to perform an app free restore operation:

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

    Right-click the <BackupSet>, point to All Tasks and then click Restore to Disk.

  2. Click OK on the Restore to Disk filter dialog. This selects All Backup Types where the Job Status is Completed.
  3. In the right pane of the Commcell Console select one of more jobs. Right click on the job and select Restore to Disk.
  4. On the Restore Options for All Selected items dialog box:
    • Select the Destination Client from the drop down list.
    • Enter the path or click Browse to specify the location of the disk to restore the application data.
    • The backup images will be restored to the disk location specified in the Restore Options for All Selected Items dialog box.
    • Click OK.

      The DB2 Agent creates a new folder with the current restore job id on the destination directory which has been specified during the restore operation. This folder contains the backup images and db2 archive logs.

      Log Files

      <restore_destination_path>/<restore_job_id>/LOGS/DB2/<Node Number>/<Chain number>/Log_files

      Example:

      cd <Restore_Destination_path>/<Restore_Jobid>

      Ls –ltr
      d rwxrwxr-x 3 db2part5 db2grp1 256 Mar 12 12:11 LOGS
      -rwxrwxr-x 1 db2part5 db2grp1 561664000 Mar 12 12:26 HPSNAP1.0.DB2PART5.NODE0001.CATN0000.20130311113930.001
      --rwxrwxr-x 1 db2part5 db2grp1 578866640 Mar 12 12:26 HPSNAP1.0.DB2PART5.NODE0000.CATN0000.20130311113921.001

      Data

      <destination directory> <Backup_images>

      You can run a disk restore using this backup image at the following location. Make sure that the SnapProtect services are running on this client.

      >cd <restore_destination_path>/<restore_job_id>
      >db2 restore database <db_name> taken at <backup_image>

      You can recover the database by reapplying the log files (roll forward).

      >db2 rollforward database <db_name> to end of logs and stop overflow log path (<Restore_Destination_path>/<Restore_Jobid>)

      The following examples are for restore and roll forward using backup images from the disk of two node DB2 MultiNode setup which has only full Backup:

      Export DB2NODE=0
      db2 terminate

      db2 restore database <Database_Name> incremental automatic from <Restore_Destination_path>/<Restore_Jobid> taken at <Node 0 Backup Image> without prompting

      Export DB2NODE=1
      db2 terminate
      db2 restore database <Database_Name> incremental automatic from <Restore_Destination_path>/<Restore_Jobid> taken at <Node 1 Backup Image> without prompting

      For roll forward:

      Export DB2NODE=0
      db2 terminate
      db2 rollforward db <Database_Name> to end of logs on all nodes overflow log path \ ( \
      <Restore_Destination_path>/<Restore_Jobid> /LOGS/<DB2 Instance>/<Database Name>/NODE0000/<Latest Chain Directory>,\
      <Restore_Destination_path>/<Restore_Jobid> /LOGS/<DB2 Instance>/<Database Name>/NODE0001/<Latest Chain Directory> on node 1 \)

      Cross Machine Restore:

      Consider the following before performing a cross machine restore to destination disk:

      • You need to restore backup images to a destination computer.
      • The destination computer's DB2 Agent must be configured in CommServe.
      • The SnapProtect path in the destination computer must be the same as source computer.
      • You must be a DB2 user to run the db2 commands for restoring to disk.

Restoring Logs

Archive logs can be restored separately or along with the database if all logs have been backed up.

By default, the log files are restored to the DB2 Retrieve Path that was specified during the installation of the DB2 Data Agent.

Archive Log restores are useful in the following scenarios:

  • If there is a database failure and you need to recover the database to the recent state, you restore all the logs along with the database.
  • If the logs from a specific time range were lost due to a hard disk corruption, you can restore them by performing a point-in-time restore of the logs.
  • In certain cases, you might need to restore only specific logs that are missing in the database. Such logs can be identified and then restored using a serial number or time ranges.

Note: For both DB2 DPF and DB2 pureScale configurations, all nodes must be available in order for a log restore to succeed.

You can use the DB2 LOGTARGET option to extract  files from the backup image and restore them to the following directory.

UNIX

<DB2_Retrieve_Path>/<db2_instance_name/<db2_database_name>/LogsFromBackupImage/

Windows

<DB2_Retrieve_Path>\<db2_instance_name\<db2_database_name>\LogsFromBackupImage\

The DB2 Retrieve Path that you can specify during installation or that you configure with an additional setting.

For additional information on LOGTARGET, go to the DB2 Knowledge Center, LOGTARGET.

Procedure

  1. From the CommCell Browser, navigate to Client Computers > client > DB2 > instance.
  2. Right-click the backup_set, point to All Tasks and then click Browse and Restore.

    The Browse and Restore dialog box is displayed.

  3. On the Time Range tab, select Latest Backup and click View Content.
  4. Select the databases to restore and click Recover All Selected.

    The Restore Options dialog box is displayed.

  5. On the Recover tab:
    1. If you want to use the DB2 LOGTARGET restore option, clear the Recover DB check box.
    2. Click Advanced.

      The Advanced Restore Options dialog box is displayed.

  6. On the Log Files tab, select the Restore Log Files check box.
  7. On the Log Files tab, select the restore log option.
    Expand All

    Restore all logs

    Select the All Log Files option.

    Restore logs to a point-in-time

    Select By Point in Time and enter the Start and End time in the boxes.

    Restore by specifying a serial number

    Select the By Log Serial Number option.

    Check the Start or End check boxes and enter the serial numbers.

    The following are the rules for specifying the serial number.

    • The end serial number must be greater than or equal to the start serial number
    • The start and the end serial number cannot be 0
    • The range of serial numbers restore can be from one or more backup jobs or from a part of a job and from one or more cycles
    • When you specify only the start sequence number, logs starting from that sequence number to the current sequence number are restored
  8. To perform the restore with the DB2 LOGTARGET option, select the Restore Logs from Backup Image (use LogTarget) check box.
  9. Optional: Select the restore options.
    Expand All

    Configuring Pre- and Post-Processes

    Run scripts before or after the restore.

    Enter the full path for the pre-recovery and post-recovery script.

    You can choose to run the post-process script even if the restore job failed. You can use the post-process script to bring a database online or to release a snapshot.

    On the Pre/Post tab:

    1. In the Pre-Recovery Command box, type the full path name for the script.
    2. In the Post-Recovery Command box, type the full path name for the script.
    3. To run the post recovery process regardless of the job's outcome, select the Run Post Process for all attempts check box.

    Restore from a copy precedence

    If the backup is corrupted, restore from a storage policy copy instead of the backup.

    For more information on modifying the copy precedence of a storage policy copy, see Copy Precedence.

    On the Copy Precedence tab, select the Restore from Copy Precedence number check box and enter a copy precedence number.

  10. Click OK to close the Advanced Restore Options dialog box.
  11. Click OK to close the Restore Options dialog box and start the restore.

Restoring the Database to a New Client

When restoring the databases to a new client, ensure the following:

  • The operating system on the destination client should be the same as that in the source client.
  • The DB2 application on the destination client should be the same (or later) version as that in the source client.
  • The DB2 user should have sufficient rights to restore the database. See Configuring User Accounts for more information.

Use the following steps to restore the database to a new client:

  1. From the CommCell Browser, navigate to Client Computers > client > DB2 MultiNode > instance.
  2. Right-click the backup_set, point to All Tasks and then click Browse and Restore.

    The Browse and Restore dialog box is displayed.

  3. On the Time Range tab, select Latest Backup and click View Content.
  4. Select the databases to restore and click Recover All Selected.

    The Restore Options dialog box is displayed.

  5. On the Recover Database tab, clear the Recover DB check box.
  6. On the General tab.
    • Select the computer that you want to restore to from the Destination Computer list.
    • Select the instance that you want to restore to from the Destination Instance list.
    • Enter the Target Database Name.
    • In the Target Database path box, enter the location of the target database.
  7. Click OK to close the Restore Options dialog box and start the restore.

Recovering Databases by Reapplying the Logs (Roll-Forward)

You can recover the database by reapplying the log files containing transactions that are not part of any database backup image. The roll-forward capability is applied after a database or table space image is restored.

Before reapplying the logs (roll-forward) on the restored database, you must perform log archiving using one or both the following configurations:

  • Enable the userexit database configuration parameter

Whenever log files are restored with the roll-forward capability, DB2 searches for the following target restore paths:

  • DB2's own directory path for log file restores

  • The retrieve Path that was specified during the installation of the DB2 Agent

  • The archive Path that was specified during the installation of the DB2 Agent

  • The path identified (if any) in the Overflow Directory field within the Roll-Forward.

If it is unable to find any of these paths, the appropriate error is reported in a file within the DB2 Audit Error Path that was specified during installation of the DB2 Agent.

To the End of Logs

Use the following steps to reapply all of the logs to the database after a restore.

  1. From the CommCell Browser, expand Client Computers > client > DB2 MultiNode > instance.
  2. Right-click the backup_set, point to All Tasks and select Browse and Restore.
  3. From the Browse window, select the tables to restore and click Recover All Selected.

    The Restore Options dialog box is displayed.

  4. On the Recover Database tab, clear the Recover DB check box.
  5. Click Advanced.

    The Advanced Restore Options dialog box is displayed.

  6. On the Roll-Forward tab.
    1. Select the Roll-forward (Reapply the Logs) check box.
    2. Select the To the End of the logs option.
    3. If the client is in a different time zone from the CommServe computer, select the destination time zone from the Time Zone list.
    4. Click OK.
  7. Click OK.

To a Point-in-Time

Use the following steps to reapply the logs till a point-in-time after a restore:

  1. From the CommCell Browser, expand Client Computers > client > DB2 MultiNode > instance.
  2. Right-click the backup_set, point to All Tasks and select Browse and Restore.
  3. From the Browse window, select the tables to restore and click Recover All Selected.

    The Restore Options dialog box is displayed.

  4. On the Recover Database tab, clear the Recover DB check box.
  5. Click Advanced.

    The Advanced Restore Options dialog box is displayed.

  6. On the Roll-Forward tab.
    1. Select the Roll-forward (Reapply the Logs) check box.
    2. Select the To a Point in Time option.
    3. Type the date and time.
    4. If the client is in a different time zone from the CommServe computer, select the destination time zone from the Time Zone list.
    5. Click OK.
  7. Click OK.

To an Alternative Log Path

Use the following steps to reapply and restore the logs in an alternative log path:

  1. From the CommCell Browser, expand Client Computers > client > DB2 MultiNode > instance.
  2. Right-click the backup_set, point to All Tasks and select Browse and Restore.
  3. From the Browse window, select the tables to restore and click Recover All Selected.

    The Restore Options dialog box is displayed.

  4. On the Recover Database tab, clear the Recover DB check box.
  5. Click Advanced.

    The Advanced Restore Options dialog box is displayed.

  6. On the Roll-Forward tab.
    1. Select the Roll-forward (Reapply the Logs) check box.
    2. Select the Alternate Log Path check box.
    3. Enter the alternative location within the DB2 directory for the log files.
    4. If the client is in a different time zone from the CommServe computer, select the destination time zone from the Time Zone list.
    5. Click OK.
  7. Click OK.

To an Overflow Directory

If the required log file is not present in the location specified by the logpath database configuration parameter, DB2 searches the overflow directory.

Use the following steps to reapply and restore the logs in an overflow directory path:

  1. From the CommCell Browser, expand Client Computers > client > DB2 MultiNode > instance.
  2. Right-click the backup_set, point to All Tasks and select Browse and Restore.
  3. From the Browse window, select the tables to restore and click Recover All Selected.

    The Restore Options dialog box is displayed.

  4. On the Recover Database tab, clear the Recover DB check box.
  5. Click Advanced.

    The Advanced Restore Options dialog box is displayed.

  6. On the Roll-Forward tab.
    1. Select the Roll-forward (Reapply the Logs) check box.
    2. Select the Alternate Log Path check box.
    3. Enter the overflow directory path in the Overflow Directory box.
    4. If the client is in a different time zone from the CommServe computer, select the destination time zone from the Time Zone list.
    5. Click OK.
  7. Click OK.

Leaving the Database in Roll Forward Pending State

Use the following steps to keep the database in a pending state till the logs are reapplied:

  1. From the CommCell Browser, expand Client Computers > client > DB2 MultiNode > instance.
  2. Right-click the backup_set, point to All Tasks and select Browse and Restore.
  3. From the Browse window, select the tables to restore and click Recover All Selected.

    The Restore Options dialog box is displayed.

  4. On the Recover Database tab, clear the Recover DB check box.
  5. Click Advanced.

    The Advanced Restore Options dialog box is displayed.

  6. On the Roll-Forward tab.
    1. Select the Roll-forward (Reapply the Logs) check box.
    2. Select the Leave in Roll-forward Pending State check box.
    3. If the client is in a different time zone from the CommServe computer, select the destination time zone from the Time Zone list.
    4. Click OK.
  7. Click OK.

Restoring a Non-recoverable Database with an Offline Backup

DB2 MultiNode supports backup and restore of an non-recoverable database.

Follow these steps.

  1. From the CommCell Browser, navigate to Client Computers | <Client> | DB2 MultiNode | <Instance>.
  2. Right-click the <BackupSet>, point to All Tasks and then click Browse and Restore.
  3. On the Browse and Restore dialog box, select Time Range and Absolute Time with the Start Time and End Time and then click View Content.
  4. Select the databases and click Recover All Selected.
  5. On the Restore Options dialog box, select the Restore Data check box and select the Entire Database option.
  6. On the Restore Options dialog box, navigate to the Recover Database tab and clear the Recover DB check box.
  7. On the Restore Options dialog box, navigate to the Restore Options tab and select an offline backup from Available Images. Click Advanced.
  8. Click OK.

Command Line Restores

We support all DB2 commands in which the –lo (load option) is used. Refer to the to the IBM DB2 manuals for the complete list of DB2 commands that can include the optional –lo parameter.

Use the following steps to restore a database using the DB2 command line.

Note: for Command line restores, disconnect all connected applications to the database before running the restore, otherwise the restore fails. The Restore parameter “Open Session” must be same as the backup number of streams.

Optional: To have the CommCell Console authenticate the job, configure the parameters for CommCell Console third-party job authentication.

For DB2 DPF

  1. At the DB2 command prompt, type the appropriate restore command for the specific platform.
    • For a DB2 instance on 32-bit AIX/Solaris, or 32-bit or 64-bit Linux, or 31-bit/64-bit Linux on System Z, run the following command:

      Export DB2NODE=<n>
      Db2 terminate
      db2 restore db <database name> incremental automatic \
      load '<software install path>/Base/libDb2Sbt.so' \
      open <n> sessions \
      taken at <backup image date of DB2NODE n > \
      without prompting

    • For a DB2 instance on 64-bit AIX/Solaris or 64bit Linux on System Z, run the following command:

      db2 restore db <database name> incremental automatic \
      load '<software install path>/Base64/libDb2Sbt.so' \
      open <n> sessions \
      open <n> sessions taken at <backup image date of DB2NODE n > \
      without prompting

  2. Roll forward the DB2 database.

    Example DB2 DPF

    export DB2NODE=0
    db2 terminate
    db2 rollforward <database name> to end of logs on all nodes and stop

For DB2 pureScale

  1. At the DB2 command prompt, type the restore command.

    db2 restore db <database name> \
    incremental automatic \
    load '<software install path>/Base/libDb2Sbt.so' \
    open <n> sessions \
    taken at <backup image date> \
    without prompting

  2. Roll forward the DB2 database.

    db2 rollforward db <database name> to end of logs and stop

Where

<software install path> is the install path for the agent software (e.g., level1/install);

<backup image date> is the date of the backup image in the following format:

"YYYYMMDDHHMMSS" (e.g., 20070612120426).

<n> is number of streams which should be equal to number of backup streams

Cross Database Restore

Prior to performing a cross database restore, configure the required parameters.

Cross Database/Cross Instance/Cross Machine Restore

Requirements:

  1. The source and target DB2 DPF databases must have the same number of nodes.
  2. SnapProtect must be installed on all target DB2 DPF machines and there must be a configured pseudo client in the CommServe.
  3. In the case of a partial restore, the DB2 DPF NODE0 tables space “SYSCATSPACE” must be part of a partial redirect restore.

Use the following steps to perform a cross-database / cross instance / cross machine restore.

For cross database restores, run all DB2 commands on the target machines for the DB2 instances/DB2 database.

For DB2 DPF

  1. At the Command Prompt, type the restore command.

    For non-automatic storage database:

    export DB2NODE=<n>
    db2 terminate

    db2 restore db <Source DB2 Database Name> \
    load '<software install path>/Base/libDb2Sbt.so' \
    open <n> sessions \
    'options "\
    CvDpfClientName=<Target MultiNode Pseudo Client Name>,\
    CvDpfControlHostName=<Target Client Name>,\
    CvSrcClientName=<Source MultiNode Pseudo Client Name>,\
    CvSrcDB2InstanceName=<Source DB2 Database Name>,\
    CvSrcDbName=<Source DB2 Database Name>"' \
    taken at <Source DB2 Database NODE<n> backup image date> \
    to '<Target DB2 Database Path>' \
    into <Target DB2 Database Name> \
    without prompting

    For automatic storage database:

    export DB2NODE=<n>
    db2 terminate

    db2 restore db <Source DB2 Database Name> \
    load '<software install path>/Base/libDb2Sbt.so' \
    open <n> sessions \
    CvDpfControlHostName=<Target Client Name>,\
    CvSrcClientName=<Source MultiNode Pseudo Client Name>,\
    CvSrcDB2InstanceName=<Source DB2 Database Name>, \
    CvSrcDbName=<Source DB2 Database Name>"' \
    taken at <Source DB2 Database NODE<n> backup image date> \
    ON '</Target DB2 Database Path>' \
    DBPATH ON '</Target DB2 Database Path>' \
    into <Target DB2 Database Name> \
    without prompting

    Where:

    n = DB2 Node Number

    CvDpfClientName = Target MultiNode Pseudo Client Name in SnapProtect CommServe

    CvDpfControlHostName = Target DB2 Client Name

    CvSrcClientName = Source MultiNode Pseudo Client Name in SnapProtect CommServe

    CvSrcDB2InstanceName = Source DB2 Database Name

    CvSrcDbName = Source DB2 Database Name

    taken at = Source DB2 Database NODE<n> backup image date

    ON = Target DB2 Database Storage Path

    DBPATH ON = Target DB2 Database Directories Path

    Into = Target DB2 Database Name

  2. Re-update the db2 database configuration parameters LOGARCHOPT1/VENDOROPT since they are overwritten by source database after restore. Set the CvSrcDbName option for the LOGARCHOPT1 parameter to the source database name.
  3. Roll forward the DB2 database.

    export DB2NODE=0
    db2 terminate

    db2 update db cfg for <database name> DBPARTITIONNUM (n) using LOGARCHOPT1 "'\
    CvDpfClientName=<Target_ Db2MultiNode_PesudeoClientName>,\
    CvDpfControlHostName=<Target_DB2_Client_Machine_Name>,\
    CvSrcClientName=<Source_ Db2MultiNode_PesudeoClientName,\
    CvSrcDB2InstanceName=<Source_DB2DPF_Instance_Name>,\
    CvSrcDbName=<Source_DB2_Database_Name>'"
    db2 update db cfg for <database name> DBPARTITIONNUM (n) using VENDOROPT "'\
    CvDpfClientName=<Target_ Db2MultiNode_PesudeoClientName>,\
    CvDpfControlHostName=<Target_DB2_Client_Machine_Name>,\
    CvSrcClientName=<Source_ Db2MultiNode_PesudeoClientName,\
    CvSrcDB2InstanceName=<Source_DB2DPF_Instance_Name>,\
    CvSrcDbName=<Source_DB2_Database_Name>'"
    db2 rollforward db <new_db> to end of logs and stop

For DB2 pureScale

  1. At the Command Prompt, type the restore command.

    db2 restore db <Source DB2 Database Name> \
    load '<software install path>/Base/libDb2Sbt.so' \
    open <n> sessions \
    'options "\
    CvDpfClientName=<Target MultiNode Pseudo Client Name>,\
    CvDpfControlHostName=<Target Client Name>,\
    CvSrcClientName=<Source MultiNode Pseudo Client Name>,\
    CvSrcDB2InstanceName=<Source DB2 Database Name>,\
    CvSrcDbName=<Source DB2 Database Name>"' \
    taken at <Source DB2 Database backup image date> \
    ON '<Target DB2 Database Path>' \
    DBPATH ON '<Target DB2 Database Path>' \
    into <Target DB2 Database Name> \
    without prompting

    Where:

    n = DB2 Node Number

    CvDpfClientName = Target MultiNode Pseudo Client Name in SnapProtect CommServe

    CvDpfControlHostName = Target DB2 Client Name

    CvSrcClientName = Source MultiNode Pseudo Client Name in SnapProtect CommServe

    CvSrcDB2InstanceName = Source DB2 Database Name

    CvSrcDbName = Source DB2 Database Name taken at = Source DB2 Database NODE<n> backup image date

    ON = Target DB2 Database Storage Path

    DBPATH ON = Target DB2 Database Directories Path

    Into = Target DB2 Database Name

  2. Re-update the db2 database configuration parameters LOGARCHOPT1/VENDOROPT since they are overwritten by source database after restore. Set the CvSrcDbName option for the LOGARCHOPT1 parameter to the source database name.

    db2 update db cfg for <database name> using LOGARCHOPT1 "'\
    CvDpfClientName=<Target_ Db2MultiNode_PesudeoClientName>,\
    CvSrcClientName=<Source_ Db2MultiNode_PesudeoClientName,\
    CvSrcDB2InstanceName=<Source_DB2DPF_Instance_Name>,\
    CvSrcDbName=<Source_DB2_Database_Name>'"

  3. Roll forward the DB2 database.

    db2 update db cfg for <database name> using VENDOROPT "'\
    CvDpfClientName=<Target_ Db2MultiNode_PesudeoClientName>,\
    CvSrcClientName=<Source_ Db2MultiNode_PesudeoClientName,\
    CvSrcDB2InstanceName=<Source_DB2DPF_Instance_Name>,\
    CvSrcDbName=<Source_DB2_Database_Name>'"
    db2 rollforward db <new_db> to end of logs and stop

Partial DB2 DPF Redirect Command Line Restore

To do a cross machine restore of NODE001 tablespaces (USERSTBS1,USERSTBS2,USERSTBS3) of two NODES on DB2 DPF instances.

Run the following DB2 commands on the Target DB2 DPF machine where the partial restore will go to. Generate a partial DB2 DPF SQL script for NODE0000 SYSCATSPACE tablespace restore.

db2 SET CLIENT ATTACH_DBPARTITIONNUM 0;
db2 SET CLIENT CONNECT_DBPARTITIONNUM 0;

db2 restore db <SourceDatabaseName> rebuild with tablespace \
\(SYSCATSPACE\) load ‘/opt/SnapProtect/Base64/libDb2Sbt.so’ \
'options "\
CvDpfClientName=DB2DPF_DB2PSCALE4_1052,\
CvSrcDpfClientName=DB2DPF_DB2PSCALE2_1052,\
CvSrcClientName=DB2DPF_DB2PSCALE2_1052,\
CvSrcDB2InstanceName=part1052,\
CvSrcDbName=PARTDB"' \
taken at <Node0 backup Image> \
ON '/database/db2/V10.5/part1052/CROSSDB1' \
DBPATH ON '/database/db2/V10.5/part1052/CROSSDB1' \
into crossdb1 \
LOGTARGET '/database/db2/V10.5/part1052/CROSSDB1/archivelogs' \
redirect \
generate script db2dpf_redirect_node0_restore.clp

After the script is run successfully, the output is a DB2 generated SQL file called db2dpf_redirect_node0_restore.clp.

Run the following DB2 commands on Target DB2 DPF machine where you want to perform to generate partial DB2 DPF SQL script for NODE0001 tablespaces (USERSTBS1,USERSTBS2,USERSTBS3) restore.

db2 SET CLIENT ATTACH_DBPARTITIONNUM 1;
db2 SET CLIENT CONNECT_DBPARTITIONNUM 1;

db2 -v restore db <SourceDatabaseName> rebuild with tablespace \
\(USERSTBS1,USERSTBS2,USERSTBS3\) \
load ‘/opt/SnapProtect/Base64/libDb2Sbt.so’ \
'options "\
CvDpfClientName=DB2DPF_DB2PSCALE4_1052,\
CvSrcDpfClientName=DB2DPF_DB2PSCALE2_1052,\
CvSrcClientName=DB2DPF_DB2PSCALE2_1052,\
CvSrcDB2InstanceName=part1052,\
CvSrcDbName=PARTDB"' \
taken at <Node1 backup Image> \
DBPATH ON '/database/db2/V10.5/part1052/CROSSDB1' \
into <TargetDatabaseName> \
LOGTARGET '/database/db2/V10.5/part1052/CROSSDB1/archivelogs' \
redirect \
generate script db2dpf_redirect_node1_restore.clp

After the script is run successfully, the output is a DB2 generated SQL file called b2dpf_redirect_restore_node1.clp .

Where

/opt/SnapProtect/Base64/libDb2Sbt.so = SnapProtect DB2 SBT library location

CvDpfClientName = Target DB2 DPF Pseudo Client Name in SnapProtect CommServe

CvSrcDpfClientName = Source DB2 DPF Pseudo Client Name in SnapProtect CommServe

CvSrcClientName = Source DB2 DPF Pseudo Client Name in SnapProtect CommServe

CvSrcDB2InstanceName = Source DB2 DPF instance Name

CvSrcDbName = Source DB2 DPF Database Name which you have Backup images of all nodes

DBPATH ON = where DB2 stores various control files for the database, given empty directory should exist with proper DB22 permission

ON = where DB2 creates automatic storage table space containers, given empty directory should exist with proper DB2 permission.

LOGTARGET = Where db2 restores the log files from a backup image, given empty directory should exist with proper DB2 permission.

Run the following DB2 scripts.

db2 –tf db2dpf_redirect_node0_restore.clp
db2 –tf db2dpf_redirect_node1_restore.clp
export DB2NODE=0
db2 terminate
db2 update db cfg for <Target_Database_Name> DBPARTITIONNUM (n) using LOGARCHOPT1 "'\
CvDpfClientName=<Target_ Db2MultiNode_PesudeoClientName>,\
CvDpfControlHostName=<Target_DB2_Client_Machine_Name>,\
CvSrcClientName=<Source_ Db2MultiNode_PesudeoClientName,\
CvSrcDB2InstanceName=<Source_DB2DPF_Instance_Name>,\
CvSrcDbName=<Source_DB2_Database_Name>'"
db2 update db cfg for <Target_Database_Name> DBPARTITIONNUM (n) using VENDOROPT "'\
CvDpfClientName=<Target_ Db2MultiNode_PesudeoClientName>,\
CvDpfControlHostName=<Target_DB2_Client_Machine_Name>,\
CvSrcClientName=<Source_ Db2MultiNode_PesudeoClientName,\
CvSrcDB2InstanceName=<Source_DB2DPF_Instance_Name>,\ CvSrcDbName=<Source_DB2_Database_Name>'"
db2 rollforward db <TargetDatabaseName> to end of backup and stop on all nodes

db2 update db cfg for <TargetDatabaseName> using LOGARCHOPT1 "''
db2 update db cfg for <TargetDatabaseName> using VENDOROPT "''"

The last two lines are for removing LOGARCHOPT1 and VENDEROPT values.

Single Job ID for Multi Stream Backups

By default, third party command line multiple stream backups share a single job in the Job Manager. Use the following steps to disable the single job ID and generate separate job IDs for each stream.

  1. From the CommCell Browser, navigate to Client Computers.
  2. Right-click the <Client> in which you want to add the additional setting, and click Properties.
  3. Click the Advanced button on the Client Properties dialog.
  4. On the Additional Setting tab on the Advanced Client Properties dialog and click the Add button.
  5. In the Name field, enter sSKIPSINGLEJOBID.
  6. In the Location box, select or enter HKEY_LOCAL_MACHINE\Software\CommVault Systems\Galaxy\Instance<xxx>\DB2Agent.
  7. In the Type box, select one of the following:
    • REG_SZ for Windows clients
    • Value for Unix clients
  8. In the Value field, type Y.
  9. Click OK.

Querying and Restoring the Data and Log Backup Images to a Disk

You can query the DB2 backup history (data and log backups) details on SnapProtect using db2util.ps1 utility on Windows and db2util.sh on UNIX and restore these backup images to a disk from the query output.

You must be a valid DB2 User to run this DB2 Utility. The CommCell user must have the browse/view capability to query DB2 backup jobs.

UNIX

  1. Use qlogin from SnapProtect/Base directory and then go to the SnapProtect/iDataAgent directory, where the db2util.sh resides.

    su – <db2instance_name>
    cd SnapProtect_location/Base
    ./qlogin –cs <commserve_name> -u <SnapProtect_user_name>
    cd SnapProtect/iDataAgent
    ./db2util.sh –q all -d <db2_db_name> -i <SnapProtect_instance_name>

  2. On the command line, type the following command to see the script options.

    ./db2util.sh -h

  3. On the command line, run the script to query the data or log backups and then restore the backups to disk.

    Usage

    ./db2util.sh -q LOG|DATA|ALL -d <db2_database_name> [-s <db2_instance_name>] [-c <client_name>] [-i <SnapProtect_instance_name>]

  4. After the job completes, use the qlogout command.

    qlogout [-cs commserver] [-all] [-tf tokenfile] [-tk token] [-h]

    Query Options

    The following options are available when you want to query SnapProtect for backup information.

    Option Description
    -q Query operation

    This can be ALL for all data and logs; LOG for logs backup history and DATA for database backup history.

    -c This is the client name presented on the CommCell Console. For a cluster setup, this client name is virtual machine client name.
    -s This is the DB2 instance name  
    -d This is the DB2 database name  
    -i This is the SnapProtect instance name.  
    -o Target database name. This is an optional option. If you do not provide this option, SnapProtect assumes the source database name to use.  
    -r Retrieves the log files under the db2 retrieve path.
    -h Prints usage information
    -a Name of the file containing the script input parameters
    -i SnapProtect Instance name. If no SnapProtect Instance is specified, Instance001 is used

    Restore Options

    The following options are available when you want to restore the data.

    Option Description
    -r Restore operation
    LOG Restore Logs to retrieve directory
    JOB Restore data and logs to a disk based on the backup job id. The logs will be restored if the backup job id contains logs.
    -d Name of database to be restored
    -j Backup job id for the data or log to be restored.
    -f Start Log Sequence number
    -t End Log sequence number
    -p Directory to which backup job data has to be restored, valid for '-r JOB' case.
    -s Source Db2 instance name
    -c Source Client name
    -n DPF To be specified for DPF clients
    -i SnapProtect Instance name
    -a Name of the file containing the script input parameters
    -i SnapProtect Instance name. If no SnapProtect Instance is specified, Instance001 is used
    • When you  you restore the backup image that is on a disk (-r parameter with JOB), a new folder with this restore Job ID  is created on the local computer in the directory that you specify in the -p option. The backup image and DB2 logs are restored under this Job ID folder. If you do not use the -p option, the system creates a new folder with the folder name dump_<JOB_ID> under the SnapProtect/Base directory. The utility restores the backup image to this directory. If you do not require the backup images, you must manually clean the dump_<JOB_ID> folder.
    • If you use  -r JOB, the -f and -t for the range of DB22 logs are ignored.
    • This command line does not support the SnapProtect (non-traditional DB2 backup image) when you provide the Job ID. All Job IDs must be the traditional DB2 jobs.
    • If you use -r LOG, the -p target location is ignored. By default, the db2 retrieve path will be used for log files restore location. The -r LOG command request both -f and -t for db2 archive log beginning sequence # and last sequence #.
    • Use this query on a cross-machine restore to query and restore the backup image to the location. You must install the DB2 application and DB2 iDataAgent on the destination . The DB2 version must be the same or higher.
    • SnapProtect supports restoring the backup image to disk using db2util.sh for a single job id only. The last job id in one cycle will be only be considered. The multiple job IDs (one cycle) in command are ignored.
    • SnapProtect supports restoring the backup image to disk using db2util.sh if the backup has multiple streams. The backup job is restored to disk with multiple images which have the same timestamps as shown in the following example:

      TESTDB.0.DB2INST7.NODE0000.CATN0000.20130719155240.001
      TESTDB.0.DB2INST7.NODE0000.CATN0000.20130719155240.002

    Input File Parameters

    You can specify the following parameters in an input file.

    Parameter Description
    CVSRCCLIENTNAME Source client name
    CVSRCDB2INSTANCENAME Source DB2 instance name
    OPERATION Specify an operation QA/QL/QD(QUERY)or RL/RJ(RESTORE) to be performed on database
    RESTOREDIR Directory to which backup job data has to be restored, valid for 'RJ' case.>
    JOBID Backup job id for the data that will be restored
    DBNAME Database name
    APPLICATION DPF Only for DPF
    FROMLSN The from log number
    TOLSN The to log number

    How to use this script to query the data, and log backups

    Use the following command to query  SnapProtect  and then display the data and log files for the DB2 instance user that is currently logged in to the specified DB2 database.

    ./db2util.sh -q LOG|DATA|ALL -d <db2_db_name> [-s <db2_instance_name>] [-c <client_name>] [-i <SnapProtect_instance_name>]

    How to use this script to restore to a disk

    Use the following command and options to restore a backup image to a disk:

    ./db2util.sh -r JOB|LOG -d <dbname> <[-j <jobId>]|[-f <from seq> -t <to seq>]> [-p <restore directory>] [-s <db2 instance name>] [-c <client name>] [-n DPF] [-i <SnapProtect_instance>]

    How to use this script to use the input file option

    Use the following command and options to restore a backup image to a disk, by using an input file that includes all the commands.

    ./db2util.sh -a <option file> [-i <SnapProtect_instance>]

    Example

    # su - db2inst5
    $ cd /opt/SnapProtect/iDataAgent
    $ ./db2util.sh -q a -d testdb -i Instance001

    Input:: DBNAME=testdb INSTANCE=Instance001

    Querying Database: testdb

    QScript[QS_querydb2backup] CS[dbserve20] DB[CommServ] SP[QS_querydb2backup]

    Qscript Output:

    jobId bkupLevel NodeNumber timeStamp streams
    ----- --------- ---------- --------- -------

    Qscript Execution Succeeded!


    QScript[QS_querydb2backup] CS[dbserve20] DB[CommServ] SP[QS_querydb2backup]

    Qscript Output:

    jobId nodeNumber chainNumber firstLogNumber lastLogNumber firstLogTime lastLogTime
    ----- ---------- ----------- -------------- ------------- ------------ -----------

    Qscript Execution Succeeded!

    $ cd /opt/SnapProtect/iDataAgent
    $ ./db2_util.sh -q a -d testdb -i Instance001

    Input:: DBNAME=testdb INSTANCE=Instance001

    Querying Database: testdb

    QScript[QS_querydb2backup] CS[dbserve20] DB[CommServ] SP[QS_querydb2backup]

    Qscript Output:

    jobId bkupLevel NodeNumber timeStamp streams
    ----- --------- ---------- --------- -------
    2742 Full NODE0000 20130204124812 1
    2745 Incr NODE0000 20130204125352 1
    2748 Delta NODE0000 20130204125907 1
    2763 Full NODE0000 20130204133429 1

Windows

Perform the following before you query for the DB2 data and log backup details and restore them to a disk:

  1. Use qlogin from SnapProtect\Base directory. You must be a valid  DB2 user to use this DB2 utility.

    qlogin -cs <cs_name>

  2. Start the powershell prompt. You can type powershell from the Windows prompt or you can start it from the command line prompt.

Use the following steps to run this script:

  1. Enable the powerShell script execution on the system:

    set db2instance=<db2_instance_name>
    powershell
    powershell Set-ExecutionPolicy Unrestricted

  2. Type the following command to get the usage information.

    PS C:\Program Files\CV\SnapProtect\iDataAgent> db2util.ps1

  3. On the command line, run the script to query the data or log backups and then restore the backups to disk.

    Usage

    db2util.ps1 -q LOG|DATA|ALL -d <db2_database_name> [-s <db2_instance_name>] [-c <client_name>] [-i <SnapProtect_instance_name>]

  4. After the job completes, use the qlogout command.

    Query Options

    The following options are available when you want to query SnapProtect  for backup information.

    Option Description
    -q Query operation

    This can be ALL for all data and logs; LOG for logs backup history and DATA for database backup history.

    -c This is the client name presented on the CommCell. For a cluster setup, this client name is virtual machine client name.
    -s This is the DB2 instance name
    -d This is the DB2 database name
    -i This is the SnapProtect instance name.
    -o Target database name. This is an optional option. If you do not provide this option, SnapProtect assumes the source database name to use.
    -r Retrieves the log files under the db2 retrieve path.
    -h Prints usage information

    Restore Options

    The following options are available when you want to restore the data.

    Option Description
    -r Restore operation
    LOG Restore Logs to retrieve directory
    JOB Restore data and logs to a disk based on the backup job id. The logs will be restored if the backup job id contains logs.
    -d Name of database to be restored
    -j Backup job id for the data or log to be restored.
    -f Start Log Sequence number
    -t End Log sequence number
    -p Directory to which backup job data has to be restored, valid for '-r JOB' case.
    -s Source Db2 instance name
    -c Source Client name
    -n DPF To be specified for DPF clients
    -i SnapProtect Instance name
    • When you  you restore the backup image that is on a disk (-r parameter with JOB), a new folder with this restore Job ID  is created on the local computer in the directory that you specify in the -p option. The backup image and DB2 logs are restored under this Job ID folder. If you do not use the -p option, the system creates a new folder with the folder name dump_<JOB_ID> under the SnapProtect\Base directory. The utility restores the backup image to this directory. If you do not require the backup images, you must manually clean the dump_<JOB_ID> folder.
    • If you use  -r JOB, the -f and -t options for the range of DB2 logs are ignored.
    • This command line does not support the SnapProtect (non-traditional DB22 backup image) when you provide the Job ID. All Job IDs must be the traditional DB2 jobs.
    • If you use -r LOG, the -p target location is ignored. By default, the db2 retrieve path will be used for log files restore location. The -r LOG command request both -f and -t for db2 archive log beginning sequence # and last sequence #.
    • Use this query on a cross-machine restore to query and restore the backup image to the location. You must install the DB2 application and DB2 iDataAgent on the destination . The DB2 version must be the same or higher.
    • SnapProtect supports restoring the backup image to disk using db2util.ps1 for a single job id only. The last job id in one cycle will be only be considered. The multiple job IDs (one cycle) in the command are ignored.
    • SnapProtect supports restoring the backup image to disk using db2util.ps1 if the backup has multiple streams. The backup job is restored to disk with multiple images which have the same timestamps as shown in the following example:

      TESTDB.0.DB2INST7.NODE0000.CATN0000.20130719155240.001
      TESTDB.0.DB2INST7.NODE0000.CATN0000.20130719155240.002

    Input File Parameters

    You can specify the following parameters in an input file.

    Parameter Description
    CVSRCCLIENTNAME Source client name
    CVSRCDB2INSTANCENAME Source DB2 instance name
    OPERATION Specify an operation QA/QL/QD(QUERY)or RL/RJ(RESTORE) to be performed on database
    RESTOREDIR Directory to which backup job data has to be restored, valid for 'RJ' case.>
    JOBID Backup job id for the data that will be restored
    DBNAME Database name
    APPLICATION DPF Only for DPF
    FROMLSN The from log number
    TOLSN The to log number

    How to use this script to query the data, and log backups

    Use the following command to query  SnapProtect  and then display the data and log files for the DB2 instance user that is currently logged in to the specified DB2 database.

    db2util.ps1 -q LOG|DATA|ALL -d <dbname> [-s <db2 instance name>] [-c <client name>] [-i <SnapProtect_instance>]

    How to use this script to restore to a disk

    Use the following command to restore a backup image to a disk:

    db2util.ps1 -r JOB|LOG -d <dbname> [-j <jobId>]|[-f <from seq> -t <to seq>] [-p <restore directory>] [-s <db2 instance name>] [-c <client name>][-n DPF] [-i <SnapProtect_instance>]

        How to use this script to use the input file option

        Use the following command to use an input options file which include all the query and restore commands for execution:

db2util.ps1 -a <option file> [-i <SnapProtect_instance>]

Example:

PS C:\Program Files\##_DOC_OEM_INSTALL_DESTINATION_COMPANY_FOLDER_##\SnapProtect\iDataAgent> .\db2util.ps1 -q a -d testdb -i Instance001

Input:: DBNAME=testdb INSTANCE=Instance001

Querying Database: testdb

QScript[QS_querydb2backup] CS[dbserve20] DB[CommServ] SP[QS_querydb2backup]

Qscript Output:

jobId bkupLevel NodeNumber timeStamp streams
----- --------- ---------- --------- -------

Qscript Execution Succeeded!


QScript[QS_querydb2backup] CS[dbserve20] DB[CommServ] SP[QS_querydb2backup]

Qscript Output:

jobId nodeNumber chainNumber firstLogNumber lastLogNumber firstLogTime lastLogTime
----- ---------- ----------- -------------- ------------- ------------ -----------

Qscript Execution Succeeded!

PS C:\Program Files\##_DOC_OEM_INSTALL_DESTINATION_COMPANY_FOLDER_##\SnapProtect\iDataAgent> .\db2util.ps1 -q a -d testdb30 -i Instance001

Input:: DBNAME=testdb30 INSTANCE=Instance001

Querying Database: testdb30

QScript[QS_querydb2backup] CS[dbserve20] DB[CommServ] SP[QS_querydb2backup]

Qscript Output:

jobId bkupLevel NodeNumber timeStamp streams
----- --------- ---------- --------- -------
2742 Full NODE0000 20130204124812 1
2745 Incr NODE0000 20130204125352 1
2748 Delta NODE0000 20130204125907 1
2763 Full NODE0000 20130204133429 1

Scheduling a Restore

For information on configuring a restore schedule, see Schedule Restores.

Managing Restore Jobs

For information on how to manage the job, see Job Controller Overview.