Symantec NetBackup status code 171 to status code 175


Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases and provides various features.

Below are some of the NetBackup status error codes from Status Code 171 to Status Code 175 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 171
Message: media id must be 6 or less characters
Explanation: operation, such as using bpmedia to suspend or freeze a media ID,
was tried 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: Whenyou loaded a volume for a backup or restore, the tape manager
(bptm), did not find the expected tape header. This error can mean that a robotic
device volume is not in the slot number that is in the Media and Device
Management volume configuration. It also can mean that a read error (I/O error)
Recommended Action: Do the following, as appropriate:
¦ If the volume is in a robot that supports bar codes, verify the robot contents
by using a robot inventory option.
¦ If the volume was mounted on a nonrobotic drive, verify that the correct volume
was mounted and assigned.
¦ Check the NetBackup Problems report. If it shows a fatal read error, try the
operation again with another drive, if possible.
¦ If your configuration has multiple servers or HBAs with access to your tape
services, make sure that the SCSI Reserve or Release is configured correctly.
(Most likely, the tape services configuration is an SSO configuration.)
More information is available on the storage server.
See the NetBackup Administrator’s Guide for UNIX and Linux, Volume II, or
See the NetBackup Administrator’s Guide for Windows Volume II

NetBackup status code: 173
Message: cannot read backup header, media may be corrupted
Explanation: When the tape manager (bptm) searches for a backup image to
restore, the following occurs: it cannot find the correct backup ID at the position
on the media where NetBackup expected it. This status code can indicate a drive
hardware problem.
Recommended Action: Do the following, as appropriate:
¦ Check the NetBackup Problems report for clues as to what caused the error.
¦ Try the restore on another drive if possible.
¦ For detailed troubleshooting information, create a debug log directory for bptm
and retry the operation. Check the resulting debug log.

NetBackup status code: 174
Message: media manager – system error occurred
Explanation: Anabnormal condition caused a tape manager (bptm) or disk manager
(bpdm) failure.
On UNIX and Linux, the file list that NetBackup generates for snapshot copy may
not have enough information to restore from the tar copy. For example, block
number information is not correct because the tar copy is not yet created.
Recommended Action: Do the following, as appropriate:
¦ Check the NetBackup Problems report to see if it shows the cause of the
problem. If you see a Problems report message similar to the following, save
all logs and call Symantec customer support:
attempted to write 32767 bytes, not a multiple of 512
¦ On UNIX and Linux, if this error occurs during a restore, the tape drive may
be incorrectly configured. It may be configured to write in fixed-length mode
when it should write in variable length mode.
Verify your drive’s configuration by comparing it to what is recommended in
the NetBackup Device Configuration Guide.
If your configuration incorrectly specifies fixed-length mode, change it to
variable length mode and suspend the media that were written on that device.
The images that were written to those media may be restorable (platform
dependent), but single file restores are likely to fail.
¦ If the problem occurs with a particular client only, verify that the client binaries
are correct, especially for bpcd.
¦ If you can read or write any other images on this media, check the following
reports for clues:
¦ Images on Media report
¦ Media Contents report

NetBackup status code: 175
Message: not all requested files were restored
Explanation: When the bptm or the bpdm process restores files from an image, it
detected a fatal error condition and terminated the restore before it completed.
Under normal circumstances, this error should not occur.
Recommended Action: Do the following, as appropriate:
¦ Check the NetBackup Problems report and the status lot or the progress log
on the client for additional information about the error.
¦ For detailed troubleshooting information, create a debug log directory for
either bptm or bpdm (whichever applies) and retry the operation. Check the
resulting debug log.

Hope this was helpful.

SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup status codes, SQL Server Frequently asked questions, SQL Server Trainings.


Leave a Reply

Your email address will not be published. Required fields are marked *