NetBackup™ Troubleshooting Guide
- Introduction
- Troubleshooting procedures
- Troubleshooting NetBackup problems
- Troubleshooting vnetd proxy connections
- Troubleshooting security certificate revocation
- Verifying host name and service entries in NetBackup
- Frozen media troubleshooting considerations
- Troubleshooting problems with the NetBackup web services
- Resolving PBX problems
- Troubleshooting problems with validation of the remote host
- Troubleshooting Auto Image Replication
- Using NetBackup utilities
- About the NetBackup support utility (nbsu)
- About the NetBackup consistency check utility (NBCC)
- About the robotic test utilities
- About the NetBackup Smart Diagnosis (nbsmartdiag) utility
- Disaster recovery
- 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
- About recovering the NetBackup catalog
- About NetBackup catalog recovery
- About recovering the entire NetBackup catalog
- About recovering the NetBackup catalog image files
- About recovering the NetBackup databases
Troubleshooting the VxUpdate add package process
When you add NetBackup VxUpdate packages through either the NetBackup web UI or the API, the packages are processed in an asynchronous manner. You can check the status of the package add process with either the GET API or the nbrepo command. Both these options list the packages that are available. If one or more of the packages being added are not available after several minutes, use the steps that are shown to determine the cause of the failure.
To troubleshoot VxUpdate package add operations:
- Use the API to confirm that the desired package is unavailable.
GET URL https://server/netbackup/deployment/packages
Or use the nbrepo command to list available packages.
Windows: install_path\NetBackup\bin\admincmd\nbrepo.exe -l
Linux: /usr/openv/netbackup/bin/admincmd/nbrepo -l
- Confirm that troubleshooting logs are present.
Windows:
install_path\NetBackup\logs\bprd
install_path\NetBackup\logs\nbwebservice
Linux:
/usr/openv/netbackup/logs/bprd
/usr/openv/logs/vxul/nbwebservice
- Review the log files around the approximate time of the package add attempt.
Search through both the
nbwebservice
and thebprd
log files for the requested VxUpdate SJA file name. - From the log files, determine the status code or status codes that the add attempt received.
- Review the recommended action for the status code in the NetBackup Status Code Guide.
The log section that is shown is from the nbwebservice
log. It shows an example of one error that can occur during the VxUpdate package add (emphasis is added for clarity):
0,51216,495,495,10738,1633618954821,12920,229,16:5F6DBAD64588994B,393:PackagesServiceImpl. validateCreatePackagesBulkInputs - The Package file for file path [\\nbserver_store\ vxupdate\NetBackup_9.1.2_VU_2of4\vxupdate_nb_9.1.2_windows_x64.sja] was not found, or is not accessible to NetBackup processes on the primary server. If the file exists, it must be in a location that is accessible to NetBackup, such as a local directory on the primary server.,61:com.netbackup.deployment.packages.service.PackagesServiceImpl,50,51216,495,495, 10739,1633618954822,12920,229,16:5F6DBAD64588994B,11659:Raised exception The Package file for file path [\\nbserver_store\vxupdate\NetBackup_9.1.2_VU_2of4\] was not found, or is not accessible to NetBackup processes on the primary server. If the file exists, it must be in a location that is accessible to NetBackup, such as a local directory on the primary server. -
The add attempt shown failed with a NetBackup Status Code 7284. The file in this example exists, but is on a network share that is not accessible to the primary server. NetBackup services such as bprd might not be active with an account that has adequate permissions to read file on UNC paths or network shares.
If you place the .sja
file into a Windows profile directory, such as a user's desktop, NetBackup generates a similar error. The error is because the NetBackup services and processes do not have adequate permissions to that location.
Review the NetBackup Status Code Guide for recommended actions.