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: 92
NetBackup™ Status Codes Reference Guide

NetBackup status code: 92

Message: media manager detected image that was not in tar format

Explanation: When you performed a restore, the tape manager (bptm) or disk manager (bpdm) did not find a tar header at the offset it expected.

Recommended Action: Do the following, as appropriate:

  • Perform a bpverify of the affected image to determine if it is written correctly.

  • Check the NetBackup Problems report for additional information about the error.

  • Verify the Media and Device Management and system configuration for the drive.

    For example, if you do not configure the drive for variable-mode block size writes on some UNIX systems, the backup images that write to the media produce this error when you attempt to restore the image.

    The following sequence of events occurs:

    • Backup succeeds.

    • Verify succeeds.

    • Restore fails.

    The bptm debug log shows an error similar to the following:

    00:58:54 [2304] <16> write_data: write of 32768 bytes indicated 
    only 29696 bytes were written, errno = 0

    In this case, configure the drive for variable-mode block sizes and suspend the media that writes on that device.

    See the NetBackup Device Configuration Guide.

    The images that were written to those media may be restorable (platform dependent), but single file restores are almost guaranteed to fail. You can expire these media and regenerate the backups. Or you can attempt to duplicate the images on these media to another device and then expire the original copy.

  • This error has occurred on re-labeled and value-added 8-mm tape drives where the drive's micro code incorrectly processes a forward space record SCSI command.

  • If the problem is not one of those discussed, create a debug log directory for either bpdm or bptm and retry the operation. Check the resulting debug log file.

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

Feedback

Was this page helpful?
Previous

NetBackup status code: 91

Next

NetBackup status code: 93

Feedback

Was this page helpful?