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™ Commands Reference Guide
  3. Appendix A. NetBackup Commands
  4. bprecover
Veritas NetBackup™ Commands Reference Guide

Name

bprecover — recover selected NetBackup related catalogs

SYNOPSIS

bprecover -wizard [-copy number]

bprecover -r -nbdb [-priority number] [-copy number] [-L output_file]

On UNIX systems, the directory path to this command is /usr/openv/netbackup/bin/admincmd/

On Windows systems, the directory path to this command is install_path\NetBackup\bin\admincmd\

DESCRIPTION

The bprecover command initiates the NetBackup utility for restoring the NetBackup catalogs. It recovers the catalogs that were backed up by using the procedures that are described in the NetBackup Administrator's Guide, Volume I. Use bprecover only if catalogs were destroyed on disk.

bprecover has three modes:

  • -wizard lets you recover the entire NetBackup catalog or the catalog image and configuration files by using a recovery wizard.

  • NBDB recovery (-r -nbdb) lets you recover the NetBackup relational database and the BMR database, if BMR is configured.

In Windows, the NetBackup catalog backup does not back up registry entries. If you reinstall NetBackup but do not provide media server names during installation, the master server is unaware of the media servers. The bprecover command returns media servers, related storage servers, and disk pools. Because these entries are not in the registry, the backup fails. Therefore, you must provide the media server names during reinstallation, or add them manually to the registry after the reinstallation.

You must have administrator privileges to run this command.

OPTIONS

-copy number

Specifies the number of the copy of the catalog backup image to be used for the recovery operation. This option restores from a non-primary copy of the catalog backup image.

-L output_file

Reports the results of the recovery in the specified output file.

-nbdb

Used with the -r option during catalog recovery to recover and resynchronize the NetBackup relational databases (NBDBs) and the BMR database (BMRDB), if BMR is configured.

For complete catalog recovery procedures, see the NetBackup Troubleshooting Guide.

-priority number

Recovers the NetBackup relational database when used with -nbdb.

-r

Recovers the images from the specified policy name.

-wizard

Enables a user to perform the same functions from a command line that are present on the recovery wizard. For example, a user can specify the full pathname to the catalog disaster recovery file or recover the entire NetBackup catalog. The wizard prompts you for the catalog disaster recovery file.

The -copy option lets you select the number of the copy

Note:

The operator must be logged on locally to the master server that is to be recovered.

EXAMPLES

Example 1 - Recover the entire NetBackup catalog or the catalog image and configuration files. On Windows, a series of screens takes you through the recovery process. On UNIX, a series of prompts takes you through the recovery process.

# bprecover -wizard

The disaster recovery information in the NetBackup Troubleshooting Guide describes each step of the recovery process.

Example 2 - Recover the NetBackup relational databases and reports the results of the recovery in the recovery.rpt file.

# bprecover -r -nbdb -L recovery.rpt

ERRORS

If any errors occur during the recover operation, NetBackup writes error messages to one of the following: stderr (UNIX systems) or the MS-DOS command window when you run the bprecover command (Windows systems).

Also, debug logs are accumulated in the following directory path:

On Windows, install_path\NetBackup\logs\admin

On UNIX, /usr/openv/netbackup/logs/admin

SEE ALSO

NetBackup Troubleshooting Guide for information on disaster recovery.

Feedback

Was this page helpful?
Previous

bprd

Next

bprestore

Feedback

Was this page helpful?