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
Issues with malware scanning
Table:
|
Error |
Description |
Workaround |
|---|---|---|
|
Failed to connect to the scan host. |
SSH connection to scan host from media server failed. |
Verify the following scan host credentials:
Refer NetBackup™ web UI Administrator's Guide for the scan host configuration. |
|
Failed to determine the scan host OS. |
Error can be due to unsupported scan host. |
Please Software Compatibility list for list of supported platforms for the scan host. |
|
Failed to copy NetBackup malware utility to the scan host. |
|
|
|
Failed to get the scan host credentials. |
Media server is not able to fetch the credentials to access scan host from the Primary. |
Check that credentials for scan host are specified. |
|
Time-out has occurred during the scan. |
Default scan operation time out is two days. Time to scan may vary depending on the factors sch as workload type, network bandwidth, backup size. |
Scan time-out is configurable and can be changed by setting configuration key. MALWARE_SCAN_ OPERATION_TIMEOUT
|
|
Failed to get response from NetBackup malware utility. |
Mismatch between |
Contact NetBackup support. |
|
Failed to launch the scanner. |
Malware scanner-specific failure message. |
Refer to |
|
Failed to mount the backup image. |
IA share is not accessible from the scan host. |
Check IA configuration on storage server. Verify on activity monitor that IA job is successful. |
|
Failed to unmount the backup image. |
IA share is busy or not accessible. |
Refer to |
|
Failed to run a scan. |
Generic failure during the scan of a backup image. |
Refer to |
|
|
|
|
All mount drives are exhausted. |
Only five backup images can be mounted at the same time on windows scan host. |
|
|
Either the Windows Defender is not installed or the environment variable is not set. |
Windows Defender is not installed on the scan host or not configured properly. |
Ensure that Microsoft Windows Defender is installed on scan host. Refer NetBackup™ web UI Administrator's Guide for the scan host configuration. |
|
Either Symantec protection engine is not installed or the environment variable is not set. |
Symantec Protection Engine is not installed on the scan host or not configured properly. |
Ensure that Symantec Protection Engine is installed on scan host. Refer NetBackup™ web UI Administrator's Guide for the scan host configuration. |
|
Failed to perform malware scan of the backup image. |
Generic error for Scan failure. |
Contact NetBackup support. |
|
Net bios name can be at most 15 chars long. |
Storage server hostname cannot be more than 15 characters for the SMB share support. If windows server 2016 is used to set up AD domain then it does not allow to join a storage server with a hostname length of more than 15 characters. |
Ensure the character limit. |
|
Failed to run a scan. |
Generic failure during scanning backup image. |
Check for the following errors:
|