Please enter search query.
Search <book_title>...
Veritas NetBackup™ Status Codes Reference Guide
Last Published:
2019-07-01
Product(s):
NetBackup (8.2)
- 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: 182
Explanation: tar cannot write to the file that is specified with the -f parameter.
Recommended Action: Do the following, as appropriate:
Create a bpcd debug log directory on the client .
On a Windows client, create a tar debug log directory.
Increase the logging level on the client:
On a UNIX client, add the VERBOSE option to the
/usr/openv/netbackup/bp.conf
file.On PC clients, increase the debug or log level.
See "Changing the logging level on Windows clients" in the NetBackup Logging Reference Guide.
Rerun the operation, check the resulting debug logs for the parameters that were passed to tar and contact Technical Support.
Click here to view technical notes and other information on the Veritas Support website about this status code.