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
- 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
- Troubleshooting error messages in the NetBackup Administration Console
- Extra disk space required for logs and temporary files for the NetBackup Administration Console
- 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 or NAT servers
- Troubleshooting issues with the NetBackup Messaging Broker (or nbmqbroker) service
- Issues with email notifications for Windows systems
- Issues with KMS configuration
- Issues with initiating the NetBackup CA migration because of large key size
- Issues with the non-privileged user (service user) account
- Issues with group name format in the auth.conf file
- Troubleshooting the VxUpdate add package process
- Issues with FIPS mode
- Issues with malware scanning
- Issues with NetBackup jobs that are enabled for data-in-transit encryption
- Issues with Unstructured Data Instant Access
- 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
- About the NetBackup Smart Diagnosis (nbsmartdiag) utility
- About log collection by job ID
- 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
- NetBackup disaster recovery email example
- About recovering the entire NetBackup catalog
- Establishing a connection with NAT media server before catalog recovery
- 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
- Index
Recovering the entire NetBackup catalog using the Catalog Recovery Wizard
This procedure describes how to recover the entire catalog using the Catalog Recovery Wizard.
See About recovering the NetBackup catalog.
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.
Note:
During the catalog recovery process, NetBackup may shut down and restart services. If NetBackup is configured as a highly available application (cluster or global cluster), freeze the cluster before you begin the recovery process. Doing so prevents a failover. Then, unfreeze the cluster after the recovery process is complete.
Warning:
Do not run any client backups before you recover the NetBackup catalog.
To recover the entire catalog by using the Catalog Recovery Wizard
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 root (administrative) privileges.
The Catalog Recovery Wizard does not work when you connect to a primary server through a change server operation.
- Start the NetBackup Administration Console.
- 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.
- In the left pane, click NetBackup Management. Then in the right pane click Recover the catalogs.
Note:
This wizard is also available on the NetBackup web UI. To recover the catalogs, on the top right, click Settings > NetBackup Catalog Recovery or on the left pane, select Recovery, and then NetBackup Catalog Recovery.
- Click Next.
- On the Catalog Disaster Recovery File panel, 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.
Note:
On the NetBackup web UI, the disaster recovery file must be available on the local computer from where you launch the NetBackup Catalog Recovery Wizard.
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 if it locates the necessary backup ID of the disaster recovery image. If the media is not located, NetBackup 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 desired and then click Next to initiate the recovery of the entire NetBackup catalog.
Note:
Unlike in the NetBackup Administration Console, you may click Cancel to terminate the NetBackup catalog recovery process on the NetBackup web UI.
- Note that the relational database transaction log is not applied during full catalog recovery.
The Recovering Catalog panel 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
Note:
You can monitor the Catalog recovery progress under Recovery Status screen of catalog recovery workflow.
Your action depends on the outcome of the recovery, as follows:
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:
In the NetBackup Administration Console, expand Security Management > Global Security Settings. In the details pane, click the Disaster Recovery tab and specify the passphrase.
Use the nbseccmd -drpkgpassphrase command to specify the passphrase.
The following warning is displayed if the disaster recovery package passphrase is not set:
WRN - Passphrase for the disaster recovery package is not set. You must set the passphrase for the catalog backups to be successful.
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 Administration Console 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