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: 92
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 Veritas Technical Support website about this status code.