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: 183
Explanation: The data that was passed to tar was corrupt.
Recommended Action: Do the following, as appropriate:
If the problem is with a UNIX client, create a
/usr/openv/netbackup/logs/tar
debug log directory on the client and rerun the operation.Check the tar debug log file for any error messages that explain the problem.
Restart the client to see if it clears the problem.
When you finish with your investigation of the problem, delete the
/usr/openv/netbackup/logs/
tar directory on the client.
If the problem is with a Microsoft Windows client, do the following in the order presented:
Create a bpcd debug log directory on the client.
On a Windows client, create a tar debug log directory.
Increase the debug or log level.
See "Changing the logging level on Windows clients" in the NetBackup Logging Reference Guide.
Rerun the operation and check the resulting debug logs.
Restart the client to see if it clears the problem.
Click here to view technical notes and other information on the website about this status code.