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
- How a host's CRL affects certificate revocation troubleshooting
- NetBackup job fails because of revoked certificate
- 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
- 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
- Using NetBackup utilities
- About NetBackup troubleshooting utilities
- About the analysis utilities for NetBackup debug logs
- 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
- 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
Troubleshooting problems with the NetBackup web server certificate
NetBackup generates and deploys an X509 certificate for the NetBackup Web Management Console (nbwmc) or NetBackup web server during installation. This certificate authenticates the NetBackup master server and validates that a client is connected to the master server. This certificate is periodically refreshed.
The NetBackup web server certificate is generated during NetBackup installation. To troubleshoot the generation of this certificate, refer to the following logs. The nbcert and nbatd logs use unified logging. The configureCerts.log uses a simple logging style and not VxUL.
usr/openv/logs/nbcert usr/openv/wmc/webserver/logs/configureCerts.log usr/openv/logs/nbatd
install_path\NetBackup\logs\nbcert C:\ProgramData\Symantec\NetBackup\InstallLogs\WMC_configureCerts_yyyymmdd_timestamp.txt install_path\NetBackup\logs\nbatd
The web server certificate has an expiration time of one year. NetBackup tries to automatically renew the certificate every 6 months. The renewed certificate is automatically deployed. Failure to renew the certificate is logged in the NetBackup error log. In such cases NetBackup tries periodically try to renew the certificate (every 24 hours). If the failure to renew the certificate persists, contact Veritas support.
To troubleshoot the certificate renewal, refer to the following logs. The nbwebservice (OID 466 and 484) and nbatd (OID 18) logs use unified logging. The configureCerts.log uses a simple logging style and not VxUL.
usr/openv/logs/nbwebservice usr/openv/wmc/webserver/logs/configureCerts.log usr/openv/logs/nbatd install_path\NetBackup\logs\nbwebservice C:\ProgramData\Symantec\NetBackup\InstallLogs\WMC_configureCerts_yyyymmdd_timestamp.txt install_path\NetBackup\logs\nbatd