NetBackup™ Troubleshooting Guide
- Introduction
- Troubleshooting procedures
- About troubleshooting procedures
- Troubleshooting NetBackup problems
- Troubleshooting installation problems
- Troubleshooting configuration problems
- Device configuration problem resolution
- Testing the primary 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
- Primary 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 primary server and client
- Example of host name and service entries on UNIX primary 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 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 web UI and 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 issues with external certificate configuration
- 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
- Troubleshooting issues with email notifications for Windows systems
- Troubleshooting issues with KMS configuration
- Troubleshooting issues with initiating the NetBackup CA migration because of large key size
- Troubleshooting issues with the non-privileged user (service user) account
- Troubleshooting issues with group name format in the auth.conf file
- Troubleshooting the VxUpdate add package process
- Troubleshooting issues with FIPS mode
- Troubleshooting issues with malware scanning
- Troubleshooting issues with NetBackup jobs that are enabled for data-in-transit encryption
- Troubleshooting issues with Unstructured Data Instant Access
- Troubleshooting issues with multifactor authentication
- Troubleshooting issues with multi-person authorization
- Troubleshooting connections to the NetBackup Scale-Out Relational Database
- 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 primary 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 the catalog backup process
- Prerequisites for recovering the NetBackup catalog or NetBackup catalog image files
- 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 databases
- 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
Recovering the primary server and Windows
This procedure assumes that all disk partitions in Windows are lost.
To recover the primary server and Windows
Install a minimal Windows operating system (perform the Express install).
Install the same type and version of Windows software that was used previously.
Install Windows in the same partition that was used before the failure.
Install any required patches. Take corrective action as needed.
Specify the default workgroup. Do not restore the domain.
Install and configure special drivers or other software that is required to get the hardware operational (for example, a special driver for the disk drive).
Install SCSI or other drivers as needed to communicate with the tape drives on the system.
Follow any hardware manufacturer's instructions that apply, such as loading the SSD on a Compaq system.
Restart the system when Windows installation is complete.
- Determine the
install_pathin which NetBackup is installed. By default, NetBackup is installed in the C:\Program Files\VERITAS directory. - Determine if any directory paths or locations need to be created for NetBackup catalog recovery.
- If necessary, partition any disks being recovered as they were before the failure. Then reformat each partition as it was before the failure.
- Reinstall NetBackup software on the server being recovered. Do not configure any NetBackup policies or devices at this time.
Note:
For the NetBackup Web Services, you must use the same user account and credentials that were used when you backed up the NetBackup catalog. More information is available:
- Install any NetBackup patches that had been previously installed. See the documentation that was included with the patch software.
- If the catalog directories differ from those in the NetBackup catalog backups, recreate that directory structure on the disk before you recover the catalog.
- If the recovery scenario involves restoring policy or catalog backups, the appropriate recovery device or devices have to be configured.
You may have to do all or some of the following tasks:
Install and configure the robotic software for the devices that read backups of the NetBackup catalog and regular backups of the disk being restored. If a non-robotic drive is available that can read these backups, then no robot is required. Although manual intervention is required if multiple pieces of media are required.
See the NetBackup Device Configuration Guide.
Discover and configure the recovery device in NetBackup.
Use the NetBackup command tpautoconf to discover and configure the recovery device in NetBackup.
See the NetBackup Commands Reference Guide.
Update the device mapping files.
- If you must restore from the policy backups or catalog backups that were done to media, the appropriate media may have to be configured in NetBackup.
See the NetBackup Administrator's Guide, Volume I.
When you configure the media, you may have to do some or all of the following:
Manually load the required media into a standalone recovery device.
Use the NetBackup utilities such as robtest or vendor-specific robotic control software to load media into the required recovery devices.
Inventory the media contents of a robotic device.
Use the vendor-specific robotic control software to load the media into the required recovery devices.
- Recover the NetBackup catalogs.
- When catalog recovery is complete, stop and restart the NetBackup services. Use the following bpdown and bpup commands, the Activity monitor, or the Services application in the Windows Control Panel.
install_path\NetBackup\bin\bpdown install_path\NetBackup\bin\bpup
Warning:
In step 12, do not restore files to the following directories:
install_path\NetBackup\db install_path\NetBackupDB install_path\NetBackup\varinstall_path\Volmgr\database
These directories were recovered in step 10 and overwriting them with regular backups leaves the catalogs in an inconsistent state. If the databases were relocated using nbdb_move from install_path\NetBackupDB\data, they are recovered in step 10 and should not be restored in step 12.
To restore all other files, do the following steps in the order presented:
Open the NetBackup web UI on the primary server.
Start the Backup, Archive, and Restore client interface.
Browse for restores and select only the partitions that were lost. Select the system directory (typically C:\Windows), which ensures that all registry files are restored.
Deselect the following directories:
install_path\NetBackup\db install_path\NetBackupDB (or relocated NetBackup database path)
install_path\NetBackup\var
install_path\Volmgr\database
See the caution in this procedure.
If you reinstall Windows, select the Overwrite existing files option, which ensures that existing files are replaced with the backups.
Start the restore.
- Restart the system, which replaces any files that were busy during the restore. When the restart process is complete, the system is restored to the state it was in at the time of the last backup.