NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

Status Codes
NetBackup 4.5 Troubleshooting Guide for Windows
◆ The third-party copy device returned an error.
If you see either of the following messages in /usr/openv/netbackup/
logs/bptm log:
cannot process extended copy error due to truncated
sense data, may be HBA problem
disk error occurred on extended copy command, key = 0x0,
asc = 0x0, ascq = 0x0 (where key, asc and ascq are all zero)
your host-bus adapter (HBA) and its driver may need to be updated, or may not be
supported by NetBackup ServerFree Agent. The host-bus adapters and drivers
supported in the release are listed in Chapter 2 of the NetBackup Release Notes.
◆ For additional troubleshooting details, refer to the Troubleshooting chapter of the
NetBackup ServerFree Agent System Administrator’s Guide.
NetBackup Status Code: 171
Message: media id must be 6 or less characters
Explanation: An operation, such as using bpmedia to suspend or freeze a media ID, was
attempted and the media ID specified was longer than six alpha-numeric characters.
Recommended Action: Retry the command with a valid media ID.
NetBackup Status Code: 172
Message: cannot read media header, may not be NetBackup media or is corrupted
Explanation: When loading a volume for a backup or restore, the tape manager (bptm),
did not find the expected tape header. This can mean that a volume in a robotic device is
not in the slot number shown in the Media Manager volume configuration or that a read
error (I/O error) occurred.
Recommended Action:
1. If the volume is in a robot that supports barcodes, verify the robot contents by using a
Media Manager robot inventory option.
2. If the volume was mounted on a nonrobotic drive, verify that the correct volume was
mounted and assigned.
3. Check the NetBackup Problems report. If a fatal read error occurred, attempt the
operation again using another drive, if possible.
124 NetBackup Troubleshooting Guide - Windows NT/2000
NetBackup 4.5 Troubleshooting Guide for Windows