GENERAL ERROR: When performing an NDMP restore, bptm logs a "NDMP_DEVICE_BUSY_ERR" error, causing the restore to appear to fail.

Article:TECH48631  |  Created: 2006-01-31  |  Updated: 2007-01-31  |  Article URL http://www.symantec.com/docs/TECH48631
Article Type
Technical Solution


Environment

Problem



GENERAL ERROR: When performing an NDMP restore, bptm logs a "NDMP_DEVICE_BUSY_ERR" error, causing the restore to appear to fail.

Solution



Overview:
When performing an Network Data Management Protocol (NDMP) restore, bptm logs a "NDMP_DEVICE_BUSY_ERR" error, causing the restore to appear to fail.  Status 83 "media open error", Status 84 "media write error" and Status 86 "media position error" have all been noted to occur in this scenario.  In cases where this issue has been seen, the data was found to have been fully restored, despite the errors incurred.

Troubleshooting:
This issue can occur when a tape device is not properly responding to 16 byte SCSI command(s) issued by NetBackup.  There is not currently a standardized method in which to tell if a drive supports 16-byte SCSI commands.  Therefore, NetBackup must be manually configured not to use 16-byte commands in order to avoid this issue.

Log Files:
The Activity Monitor on the master server will show:
11/03/2005 11:00:19 - begin Restore
11/03/2005 11:00:24 - media needed: YU0045
11/03/2005 11:00:24 - restoring from image <image_name>
11/03/2005 11:00:32 - connecting
11/03/2005 11:00:33 - connected; connect time: 0:00:00
11/03/2005 11:00:33 - started process bptm (pid=17624)
11/03/2005 11:00:36 - requesting resource YU0045
11/03/2005 11:00:36 - awaiting resource YU0045. Waiting for resources.
         Reason: Media is in use, Media server: N/A,
         Robot Type(Number): NONE(0), Media ID: YU0045, Drive Name: N/A,
         Volume Pool: N/A, Storage Unit: N/A, Drive Scan Host: N/A
11/03/2005 11:03:01 - Error bptm (pid=17624) cannot open ndmp device nrst2a,
error code 2 (NDMP_DEVICE_BUSY_ERR)
11/03/2005 11:02:58 - granted resource YU0045
11/03/2005 11:02:58 - granted resource entnrst2a
11/03/2005 11:03:01 - current media YU0045 complete, requesting next media
entnrst2a:NetBackup:YU0045
11/03/2005 11:03:49 - started process bptm (pid=17624)
11/03/2005 11:03:49 - mounting YU0045
11/03/2005 11:03:49 - granted resource YU0045
11/03/2005 11:03:49 - granted resource entnrst2a
11/03/2005 11:04:20 - mounted YU0045; mount time: 0:00:31
11/03/2005 11:04:20 - positioning YU0045 to file 19
11/03/2005 11:04:36 - positioned YU0045; position time: 0:00:16
11/03/2005 11:04:37 - begin reading
11/03/2005 11:06:56 - end reading; read time: 0:02:19
11/03/2005 11:07:03 - Error bpbrm (pid=17610) client restore EXIT STATUS 83:
media open error
11/03/2005 11:07:04 - restored from image <image_name>;
restore time: 0:06:40
11/03/2005 11:07:06 - end Restore; elapsed time 0:06:47
the restore failed to recover the requested files (5)

Resolution:
Add the "NO_SIXTEEN_BYTE_CDB" touch file to the Media Server in question.  This disables the use of 16 byte CDB commands.

Create the following blank (touch) file on the Media Server in question:

Unix Media Servers:
/usr/openv/volmgr/database/NO_SIXTEEN_BYTE_CDB

Windows Media Servers:
<install_dir>\Volmgr\database\NO_SIXTEEN_BYTE_CDB

Alternatively, some drives may have a firmware update available that allows the use of these commands, so that the above touch file is not needed.

Supplemental Materials

SourceError Code
Value83
DescriptionNetBackup Error 83: media open error

SourceError Code
Value5
DescriptionNetBackup Error 5: the restore failed to recover the requested files

SourceError Code
Value86
DescriptionNetBackup Error 86: media position error

SourceError Code
Value84
DescriptionNetBackup Error 84: media write error


Legacy ID



284513


Article URL http://www.symantec.com/docs/TECH48631


Terms of use for this information are found in Legal Notices