Backups ending in Status code 174

[bpACH]

Hello,

We are currently using Veritas Netbackup 6.0 mp3.

Our backups are ending with status code 174.

When we look at the activity monitor the job reports:

NDMP backup failed: path= UNKNOWN

Looking at the bptm logs, we find the following error:

20:49:18.162 [11713] <2> drivename_open: Called with Create 1, file QUANTUM.SDLT320.002
20:49:18.163 [11713] <2> drivename_lock: lock failed
20:49:18.163 [11713] <2> drivename_close: Called
20:49:18.163 [11723] <2> drivename_open: Called with Create 1, file QUANTUM.SDLT320.003
20:49:18.163 [11723] <2> drivename_lock: lock failed
20:49:18.163 [11723] <2> drivename_close: Called

The drives that call this are physically empty and NetBackup will report them as active for a while after the error occurs.

 

[bpACH]

Issue resolved.

1. Stopped Netbackup
2. Deleted the files in /usr/openv/netbackup/db/media/drives
3. Started Netbackup

 

[Mikehi]

Status Code: 174
Message: media manager system error occurred
Explanation: An abnormal condition occurred causing a tape manager (bptm) or disk
manager (bpdm) failure. This should not occur under normal circumstances.
Note: If this occurs on a Sequent platform and you are attempting to back up more than four
gigabytes of data, save all your logs and call VERITAS technical support. For other
platforms perform the recommended actions described below.
Recommended Action:
1. Check the NetBackup Problems report to see if it shows the cause of the problem. If you
see a Problems report message similar to "attempting to write 32767 bytes, not a multiple of
1024" save all logs and call VERITAS customer support.
2. On UNIX, if this occurs during a restore, it may be that the tape drive is incorrectly
configured to write in fixed length mode when it should write in variable length mode.
Verify your drive's configuration, comparing it to what is recommended in the Media
Manager Device Configuration Guide (also see Step 7 of this procedure).
If your configuration incorrectly specifies fixed length mode, change the configuration to
specify variable length mode and suspend media that were written on that device. The
images written to those media may be restorable (this is platform dependent), but single file
restores are almost guaranteed to fail.
3. If you see the problem with only one client, verify that the client binaries are correct,
especially those for bpcd.
4. Can you read or write any other images on this media?
If so, the check the following reports for clues:
• Images on Media report
• Media Contents report
5. Verify the following:
• The media by using the NetBackup image verify option.
• That you are using the correct media type for the device.
6. Check the system or console log for errors (on UNIX) or the Event Viewer Application log
(on Windows NT).
7. For detailed debug information, create an activity log directory for either bptm or bpdm
(whichever applies) and retry the operation. Check the resulting activity log.
If the bptm activity log shows an error similar to
00:58:54 [2304] <16> write_data: write of 32768 bytes indicated only 29696 bytes were
written, errno = 0
it may be that the tape drive is configured to write in fixed length mode rather than variable
length mode, and the image being written encountered the end-of-media.
Take the corrective action suggested in Step 2.

regards