Please enter search query.
Search <book_title>...
NetBackup™ Troubleshooting Guide
Last Published:
2022-09-08
Product(s):
NetBackup (10.1)
- 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
- 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 initiating the NetBackup CA migration because of large key size
Initiating the NetBackup CA migration may be timed out during installation or upgrade because of large key size.
Following is an example of the error that is logged in the installation logs:
06-19-2020,20:40:39 : Initiating the NetBackup CA migration with 16384 bits key size.
06-19-2020,20:40:39 : NetBackup security service is still generating key pairs with key size of 16384 bits.
06-19-2020,20:40:39 : NetBackup will recheck the status of the NetBackup CA migration initiation phase after every 30 seconds
06-19-2020,20:40:40 : The NetBackup CA migration initiation process is taking more time than expected
06-19-2020,20:40:40 : Failed to set up the new NetBackup CA
06-19-2020,20:40:40 : network connection timed out(Error code: 41)
06-19-2020,20:40:40 : Command returned status 41
06-19-2020,20:40:40 : "C:\Program Files\Veritas\NetBackup\bin\admincmd \nbseccmd.exe" -nbcamigrate -initiatemigration -quiet -keysize 16384 -reason "Upgrade" -installtime, ERROR: nbseccmd.exe failed with error status: 41
In case of such an error, it is possible that the CA migration was successfully initiated but the request is timed out because of the large key size. However, in the background the CA migration initiation may be complete and the certificates may be renewed with the new CA.
To verify if the initiation of NetBackup CA migration was successful
- Run the following command:
nbseccmd -nbcaMigrate -summary
- Check if the NetBackup CA migration status is INITIATED.
If the migration status is NO_MIGRATION, it implies that the CA migration has failed during installation.
Initiate a new migration using the following command:
nbseccmd -nbcaMigrate -initiateMigration | -i -keysize <key-value> [-reason <comment>] [-json] [-quiet]
- Once you have ensured that the migration status is INITIATED, run the following command to verify if the new CA is displayed in the list:
nbseccmd -nbcalist
If the new CA is present in the list, it implies that the migration is successfully initiated.
If the new CA is not present in the list, run the following command:
nbseccmd -nbcaMigrate -syncMigrationDB
- If the certificates are still not updated, contact Veritas Technical Support.