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™ Status Codes Reference Guide
  3. NetBackup status codes
  4. NetBackup status codes
  5. NetBackup status code: 182
NetBackup™ Status Codes Reference Guide

NetBackup status code: 182

Message: tar received an invalid file name

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 Veritas Technical Support.

Click here to view technical notes and other information on the Veritas Technical Support website about this status code.

Feedback

Was this page helpful?
Previous

NetBackup status code: 181

Next

NetBackup status code: 183

Feedback

Was this page helpful?