Veritas NetBackup™ Status Codes Reference Guide
- NetBackup status codes
- NetBackup status codes
- NetBackup KMS status codes
- NetBackup status codes
- Media Manager status codes
- Media Manager status codes
- Media Manager status codes
- Device configuration status codes
- Device configuration status codes
- Device configuration status codes
- Device management status codes
- Device management status codes
- Device management status codes
- Robotic status codes
- Robotic status codes
- Robotic status codes
- Robotic error codes
- Robotic error codes
- Robotic error codes
- Security services status codes
- Security services status codes
- Security services status codes
- NetBackup alert notification status codes
NetBackup status code: 130
Explanation: An error occurred that prevents the product from operating in a consistent fashion. This error is usually related to a system call. The NetBackup APIs can report this error when an unexpected internal error occurs in processing the request.
Recommended Action: Do the following, as appropriate:
Check the NetBackup Problems report for additional information about the error.
Check the system log for reported problems.
For detailed troubleshooting information, create bpdbm, bptm, and bprd debug log directories on the master server. Increase the unified logging level by using the vxlogcfg command.
See "About unified logging" in the NetBackup Logging Reference Guide.
Retry the operation and check the resulting debug logs.
If the policy validation fails, it is due to one of following reasons:
A certificate mismatch is present on the client. Remove the CloudPoint CA certificate from the following location and validate the policy again:
install_location/var/global/cloudpoint_certificates
The CloudPoint server is not accessible.
If the NetBackup APIs produce this error, examine the unified logs for
nbwebservice
on the master server. For details on the web services logs, see the section on the NetBackup Web Services logging within the NetBackup Logging Reference Guide.
When a VMware agentless restore is performed, the restore can cause one of the following issues:
Failed to stage recovery tool on path %s in destination VM %s with error code %d.
Make sure that the staging location path that is used exists and the provided target VM credentials have root or admin privileges.
Failed to get the staging location for destination VM %s with error %d.
Make sure that there is TMP or TEMP environment path available in the target VM or provided target VM credentials has root or admin privileges.
Failed to retrieve the guest VM%s operating system (OS) details with error code %d.
Make sure that latest VMware Tools are installed and running in the target VM.
Click here to view technical notes and other information on the website about this status code.