Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ Troubleshooting Guide
  3. Troubleshooting procedures
  4. Troubleshooting the VxUpdate add package process
NetBackup™ Troubleshooting Guide

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:

  1. 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

  2. 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

  3. Review the log files around the approximate time of the package add attempt.

    Search through both the nbwebservice and the bprd log files for the requested VxUpdate SJA file name.

  4. From the log files, determine the status code or status codes that the add attempt received.
  5. Review the recommended action for the status code in the NetBackup Status Code Guide.
Example

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\
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. - errorCode: 7284

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.

Feedback

Was this page helpful?
Previous

Troubleshooting issues with group name format in the auth.conf file

Next

Troubleshooting issues with FIPS mode

Feedback

Was this page helpful?