Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Veritas NetBackup™ for DB2 Administrator's Guide
  3. Performing backups and restores of DB2
  4. Performing a database restore
  5. Using the NetBackup for DB2 recovery wizard
  6. Using the recovery wizard
Veritas NetBackup™ for DB2 Administrator's Guide

Using the recovery wizard

When you are ready to perform a recovery, complete the following procedure to create and run a template with the recovery wizard. When you run a template, all restore operations are performed before any and all roll-forward operations.

Note the following:

  • When you perform a DB2 restore, false alarms are reported in the NetBackup Activity Monitor. DB2 accesses the NetBackup image twice when you perform a restore. The first access reads a partial image, which is reported as "The restore failed to recover the requested files" (status 5) in the Activity Monitor. The next access reads the entire image, which should result in a successful restore (status 0). The template execution status, not the activity monitor, is the best indication of overall success.

  • DB2 warning SQL2539W indicates that the requested restore operation replaces the existing database. That is, the existing database files are deleted. When running a template to perform a restore, this warning is logged and the restore proceeds without interruption.

  • DB2 warning SQL2523W indicates that the backup image originates from a different database of the same name. This warning is handled as an error to prevent DB2 from deleting log files.

  • DB2 error SQL1260N indicates that the restored partition is not configured for roll-forward recovery. If the template is configured to perform a roll-forward, this step is skipped.

To use the recovery wizard

  1. Log onto NetBackup as the DB2 user.
  2. In the Backup, Archive, and Restore interface, do one of the following:

    Windows: Choose File > Select Files and Folders to Restore > from Normal Backup

    UNIX: Click the Restore Files tab.

  3. Expand a DB2 instance and select the database objects you want to restore.
  4. Windows: Click Actions > Restore

    UNIX: Click Restore.

  5. Enter information about the restore operation you want to perform in the following screens:

    • Welcome

    • Database Login

    • Time Periods

    • Restore Options

    • Recovery Options

    If you need an explanation of any of the fields on the wizard screens or more details, click Help on the wizard screen.
  6. Run the template immediately after the wizard finishes, to save the template locally, or both. For explanations of your choices, click Help.

    Template execution does not support the use of local time when performing a roll-forward. The roll-forward time that is specified in the template is passed to DB2, and it is interpreted as GMT by DB2. For more information, see the ROLLFORWARD command in your DB2 documentation.

More Information

Performing a database restore

Using the Backup, Archive, and Restore interface to browse DB2 resources

Using bpdbsbdb2 for a database restore

Using DB2 to perform a restore

NetBackup for DB2 backup overview

Feedback

Was this page helpful?
Previous

Selecting files for restore

Next

Using bpdbsbdb2 for a database restore

Feedback

Was this page helpful?