Veritas NetBackup™ Troubleshooting Guide
- Introduction
- Troubleshooting procedures
- About troubleshooting procedures
- Troubleshooting NetBackup problems
- Troubleshooting installation problems
- Troubleshooting configuration problems
- Device configuration problem resolution
- Testing the master server and clients
- Testing the media server and clients
- Resolving network communication problems with UNIX clients
- Resolving network communication problems with Windows clients
- Troubleshooting vnetd proxy connections
- vnetd proxy connection requirements
- Where to begin to troubleshoot vnetd proxy connections
- Verify that the vnetd process and proxies are active
- Verify that the host connections are proxied
- Test the vnetd proxy connections
- Examine the log files of the connecting and accepting processes
- Viewing the vnetd proxy log files
- Troubleshooting security certificate revocation
- Troubleshooting cloud provider's revoked SSL certificate issues
- Troubleshooting cloud provider's CRL download issues
- How a host's CRL affects certificate revocation troubleshooting
- NetBackup job fails because of revoked certificate or unavailability of CRLs
- NetBackup job fails because of apparent network error
- NetBackup job fails because of unavailable resource
- Master server security certificate is revoked
- Determining a NetBackup host's certificate state
- Troubleshooting issues with external CA-signed certificate revocation
- About troubleshooting networks and host names
- Verifying host name and service entries in NetBackup
- Example of host name and service entries on UNIX master server and client
- Example of host name and service entries on UNIX master server and media server
- Example of host name and service entries on UNIX PC clients
- Example of host name and service entries on UNIX server that connects to multiple networks
- About the bpclntcmd utility
- Using the Host Properties window to access configuration settings
- Resolving full disk problems
- Frozen media troubleshooting considerations
- Troubleshooting problems with the NetBackup web services
- Troubleshooting problems with the NetBackup web server certificate
- Resolving PBX problems
- Troubleshooting problems with validation of the remote host
- About troubleshooting Auto Image Replication
- Troubleshooting network interface card performance
- About SERVER entries in the bp.conf file
- About unavailable storage unit problems
- Resolving a NetBackup Administration operations failure on Windows
- Resolving garbled text displayed in NetBackup Administration Console on a UNIX computer
- Unable to logon to the NetBackup Administration Console after external CA configuration
- Troubleshooting file-based external certificate issues
- Troubleshooting Windows certificate store issues
- Troubleshooting backup failures
- Troubleshooting backup failure issues with NAT clients
- Troubleshooting issues with the NetBackup Messaging Broker (or nbmqbroker) service
- Using NetBackup utilities
- About NetBackup troubleshooting utilities
- About the analysis utilities for NetBackup debug logs
- About the Logging Assistant
- About network troubleshooting utilities
- About the NetBackup support utility (nbsu)
- About the NetBackup consistency check utility (NBCC)
- About the NetBackup consistency check repair (NBCCR) utility
- About the nbcplogs utility
- About the robotic test utilities
- Disaster recovery
- About disaster recovery
- About disaster recovery requirements
- Disaster recovery packages
- About disaster recovery settings
- Recommended backup practices
- 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
- Generating a certificate on a clustered master server after disaster recovery installation
- About restoring disaster recovery package
- About the DR_PKG_MARKER_FILE environment variable
- Restoring disaster recovery package on Windows
- Restoring disaster recovery package on UNIX
- About recovering the NetBackup catalog
- About NetBackup catalog recovery on Windows computers
- About NetBackup catalog recovery from disk devices
- About NetBackup catalog recovery and symbolic links
- About NetBackup catalog recovery and OpsCenter
- NetBackup disaster recovery email example
- About recovering the entire NetBackup catalog
- About recovering the NetBackup catalog image files
- About recovering the NetBackup relational database
- Recovering the NetBackup catalog when NetBackup Access Control is configured
- Recovering the NetBackup catalog from a nonprimary copy of a catalog backup
- Recovering the NetBackup catalog without the disaster recovery file
- Recovering a NetBackup user-directed online catalog backup from the command line
- Restoring files from a NetBackup online catalog backup
- Unfreezing the NetBackup online catalog recovery media
- Steps to carry out when you see exit status 5988 during catalog recovery
About recovering the NetBackup catalog
Before you recover the NetBackup catalog, you must do the following:
Ensure that NetBackup is running in the recovery environment.
Configure the recovery devices NetBackup.
Ensure that the media on which the catalog backups exist are available to NetBackup.
If the NetBackup master server is part of a cluster, ensure that the cluster is functional.
Restore the NetBackup host identity by restoring the disaster recovery package.
See About restoring disaster recovery package.
Caution:
After successful catalog recovery, you must set the disaster recovery package passphrase, because the passphrase is not recovered during the catalog recovery.
The NetBackup catalog consists of several parts. How you recover the catalog depends on which part or parts of the catalog you want to recover, as follows:
Table: Catalog recovery options
Recovery option | Description |
|---|---|
Recover the entire catalog | Veritas recommends that you recover the entire catalog. Doing so helps ensure consistency among the various parts of the catalog. This method is most useful for recovering a catalog to the same environment from which it was backed up. |
Recover the catalog image files and configuration files | The image database contains information about the data that has been backed up. The configuration files ( This type of recovery also restores the NetBackup relational database (NBDB) to the staging directory so that it is available for further processing if required. |
Recover the relational database files | The NetBackup database (NBDB) is also known as the Enterprise Media Manager (EMM) database. It contains information about volumes and the robots and drives that are in NetBackup storage units. The NetBackup relational database also contains the NetBackup catalog images files. The images files contain the metadata that describes the backups. Recover the relational database if it is corrupt or lost but the catalog image files exist and are valid. |
Recovery of the entire catalog or the catalog image files relies on the disaster recovery information. That information is saved in a file during the catalog backup. The location of the disaster recovery file is configured in the catalog backup policy.
See NetBackup disaster recovery email example.
If you do not have the disaster recovery file, you still can recover the catalog. However, the process is much more difficult and time-consuming.
See Recovering the NetBackup catalog without the disaster recovery file.
Note:
After a catalog recovery, NetBackup freezes the removeable media that contains the catalog backup. This operation prevents a subsequent accidental overwrite action on the final catalog backup image on the media. This final image pertains to the actual catalog backup itself, and its recovery is not part of the catalog recovery. You can unfreeze the media.
Other procedures exist for special use cases.
See Recovering the NetBackup catalog when NetBackup Access Control is configured.
Other topics provide more information about catalog recovery.
See About NetBackup catalog recovery on Windows computers.
More Information