NetBackup™ Troubleshooting Guide
- Introduction
- Troubleshooting procedures
- Troubleshooting NetBackup problems
- Troubleshooting vnetd proxy connections
- Troubleshooting security certificate revocation
- Verifying host name and service entries in NetBackup
- Frozen media troubleshooting considerations
- Troubleshooting problems with the NetBackup web services
- Resolving PBX problems
- Troubleshooting problems with validation of the remote host
- Troubleshooting Auto Image Replication
- Using NetBackup utilities
- About the NetBackup support utility (nbsu)
- About the NetBackup consistency check utility (NBCC)
- About the robotic test utilities
- About the NetBackup Smart Diagnosis (nbsmartdiag) utility
- Disaster recovery
- About disk recovery procedures for UNIX and Linux
- About clustered NetBackup server recovery for UNIX and Linux
- About disk recovery procedures for Windows
- About clustered NetBackup server recovery for Windows
- About recovering the NetBackup catalog
- About NetBackup catalog recovery
- About recovering the entire NetBackup catalog
- About recovering the NetBackup catalog image files
- About recovering the NetBackup databases
Recovering the entire NetBackup catalog using the NetBackup catalog recovery wizard
This procedure describes how to recover the entire catalog using the NetBackup catalog recovery wizard.
Note:
Full catalog recovery restores the device and the media configuration information in the catalog backup. If you must configure storage devices during the recovery, Veritas recommends that you recover only the NetBackup image files.
Warning:
Do not run any client backups before you recover the NetBackup catalog.
To recover the entire catalog by using the NetBackup catalog recovery wizard
- Review the prerequisites before starting the catalog recovery.
See Prerequisites for recovering the NetBackup catalog or NetBackup catalog image files.
If NetBackup is not running, start all of the NetBackup services by entering the following:
On UNIX and Linux:
/usr/openv/netbackup/bin/bp.start_all
On Windows:
install_path\NetBackup\bin\bpup
- Sign into the primary server on which you want to recovery the catalog. You must have the Administrator role or similar permissions.
- Start the NetBackup web UI.
- If the catalog backup and the recovery devices are not available, do the following:
Configure the necessary recovery device in NetBackup.
For tape storage or BasicDisk storage, see the NetBackup Administrator's Guide, Volume I. For disk storage types, see the guide that describes the option. See the following website for NetBackup documentation:
If the catalog backup was written to an immutable (MSDP WORM) storage server, add the storage server back to the primary server's configuration with the CLI nbdevconfig command. See the NetBackup Commands Reference Guide for more information about the command.
Make the media that contains the catalog backup available to NetBackup: Inventory the robot or the disk pool, add the media for standalone drives, configure the storage server and disk pool, or so on.
For tape storage or BasicDisk storage, see the NetBackup Administrator's Guide, Volume I. For disk storage types, see the guide that describes the option.
- At the top, click Settings > NetBackup catalog recovery.
- Specify where the disaster recovery file is stored. You can browse to select the file or enter the full pathname to the disaster recovery file. The disaster recovery file must be available on the local computer from where you opened the web UI.
In most cases, you specify the most recent disaster recovery information file available. If the most recent catalog backup is an incremental backup, use the disaster recovery file from the incremental backup. (There is no need to first restore the full backup and then follow with the incremental backup.)
If some form of corruption has occurred, you may want to restore to an earlier state of the catalog.
Click Next to continue.
- NetBackup searches for the media that are required to recover the catalog. It then informs you of the progress and locates the necessary backup ID of the disaster recovery image. If the media is not located, NetBackup indicates which media is needed to update the database.
If necessary, follow the instructions to insert the media that is indicated and run an inventory to update the NetBackup database. The information that displays depends on whether the recovery is from a full backup or an incremental backup.
When all the required media sources are found, click Next.
- By default, the Recover entire NetBackup catalog option is selected.
Select a Job priority if wanted and then click Next to initiate the recovery. You can click Cancel to stop the NetBackup catalog recovery process.
- Your action depends on the outcome of the recovery, as follows:
NetBackup displays the progress of the recovery of the various catalog components:
NBDB database (including the EMM database)
BMR database (if applicable)
NetBackup policy files
Backup image files to their proper image directories
Other configuration files
Not successful
Consult the log file messages for an indication of the problem. Click Cancel, fix the problem, and then run the wizard again.
Successful
Click Next to continue to the final wizard panel.
- After the recovery completes, click Finish.
- Important: After successful catalog recovery, you must set the disaster recovery package passphrase. The passphrase is not recovered during the catalog recovery.
Do one of the following to set the passphrase:
At the top, click Settings > Global security. On Disaster recovery tab specify the passphrase.
Use the nbseccmd -drpkgpassphrase command to specify the passphrase.
Before you continue, be aware of the following points:
If you recovered the catalog from removable media, NetBackup freezes the catalog media.
Before you restart NetBackup, freeze the media that contains the backups more recent than the date of the catalog from which you recovered.
NetBackup does not run scheduled backup jobs until you stop and then restart NetBackup.
You can submit backup jobs manually before you stop and restart NetBackup. However, you must freeze the media that contains the backups more recent than the date of the catalog from which you recovered. Otherwise, NetBackup may overwrite that media.
- Clean up the allowed list cache on all hosts.
- If the NetBackup web UI is active on any of the hosts, the command that stops the NetBackup services shuts it down.
Stop and restart NetBackup services on the primary server and other hosts, as follows:
On UNIX and Linux:
/usr/openv/netbackup/bin/bp.kill_all /usr/openv/netbackup/bin/bp.start_all
On Windows:
install_path\NetBackup\bin\bpdown install_path\NetBackup\bin\bpup
- After the services are restarted, run one of the following commands:
If NetBackup (or host ID-based) certificates are used in your NetBackup domain, do the following:
On a non-clustered setup:
UNIX:
/usr/openv/netbackup/bin/nbcertcmd -renewcertificate
Windows:
install_path\netbackup\bin\nbcertcmd -renewcertificate
On a clustered setup:
UNIX:
/usr/openv/netbackup/bin/nbcertcmd -renewcertificate -cluster
Windows:
install_path\netbackup\bin\nbcertcmd -renewcertificate -cluster
If external CA-signed certificates are used in your NetBackup domain, do the following:
On a non-clustered setup
UNIX:
/usr/openv/netbackup/bin/nbcertcmd -enrollCertificate
Windows:
install_path\netbackup\bin\nbcertcmd -enrollCertificate
On a clustered setup:
UNIX:
/usr/openv/netbackup/bin/nbcertcmd -enrollCertificate -cluster
Windows:
install_path\netbackup\bin\nbcertcmd -enrollCertificate -cluster
If the command runs successfully, proceed with the next step.
If the command fails with the exist status 5988, refer to the following topic:
See Steps to carry out when you see exit status 5988 during catalog recovery.
Proceed with the next step.
- If the catalog recovery is part of a server recovery procedure, complete the remaining steps in the appropriate recovery procedure.
Recovery can include the following:
Importing the backups from the backup media into the catalog.
Write protecting the media.
Ejecting the media and setting it aside.
Freezing the media.
Note:
A catalog recovery changes the configuration of NetBackup back to the point in time of the catalog backup. Any change to the configuration after the point-in-time of the catalog backup (For example: changes to policies, clients, storage units) must be re-applied if those changes are desired. These changes should be re-applied before new backups are taken. If the changes are not applied, they can affect what is protected and how the protection is managed.
As an example, a storage unit might have been modified to require the use of WORM locking on new images. If WORM locking isn't re-applied, new backups do not have the desired WORM protections.
More Information