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: 174
Explanation: An abnormal condition caused a tape manager (bptm) or disk manager (bpdm) failure.
On UNIX, the file list that NetBackup generates for snapshot copy may not have enough information to restore from the NetBackup tar
copy. For example, block number information is not correct because the NetBackup 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 contact Veritas Technical Support:
attempted to write 32767 bytes, not a multiple of 512
On UNIX, 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
Verify the following:
The media, by using the NetBackup image verify option.
That you used the correct media type for the device.
Check the system or the console log for errors (on UNIX) or the Event Viewer Application log (on Windows).
For detailed debug information, create a debug log directory for either bptm or bpdm (whichever applies) and retry the operation. Check the resulting debug log.
On UNIX, if the bptm debug log shows an error similar to the following, the tape drive is configured to write in fixed-length mode rather than variable length mode.
00:58:54 [2304] <16> write_data: write of 32768 bytes indicated only 29696 bytes were written, errno = 0
The image being written encountered the end-of-media.
If the backup was configured for an OpenStorage disk storage unit, the OpenStorage vendor's plug-in may not be installed on all media servers in the storage unit's media server list. Either install the vendor plug-in on all of the media servers or remove from the list the servers that do not have the plug-in installed.
On UNIX, if this error occurs during a restore, refresh the Backup, Archive, and Restore client console and retry the restore. This action refreshes the file list displayed in the client console and passes the correct information about the selected files.
Click here to view technical notes and other information in the Veritas Knowledge Base about this status code.