GENERAL ERROR: Tape drives in use for NDMP backups would got to a down status while a job was active.

Article:TECH56990  |  Created: 2008-01-23  |  Updated: 2009-01-22  |  Article URL http://www.symantec.com/docs/TECH56990
Article Type
Technical Solution


Environment

Issue



GENERAL ERROR: Tape drives in use for NDMP backups would got to a down status while a job was active.

Error



media write error

Solution



Overview:
Backups would run anywhere from minutes to hours at which point Tape Drives would change to a down status.  

Error Code(s)/Message(s):
NetBackup Exit Status 84 (media write error)

Troubleshooting:
The bptm log file showed the following:
set_job_details: LOG 1196768528 16 bptm 5676 ERR - Cannot write TIR data to media, NDMP return code 18.
set_job_details: Done
job_monitoring_exex: ACK disconnect
job_disconnect: Disconnected
db_error_add_to_file: dberrorq.c:midnite = 1196748000
write_data_tir: ERR - Cannot write TIR data to media, NDMP return code 18.
send_MDS_msg: DEVICE_STATUS 1 10217 dcback01 DC1297 4000508 HPULTRIUM3-SCSIHU10625WWRhcart3 2000298 WRITE_ERROR 0 0
emmlib_handleMessage: (0) CORBA call returned 0
log_media_error: successfully wrote to error file - 12/04/07 05:42:08 DC1297 3 WRITE_ERROR HPULTRIUM3-SCSIHU10625WWRhcart3
check_error_history: just tpunmount: called from bptm line 19635, EXIT_Status = 84
io_close: closing C:\VERITAS\NetBackup\db\media\tpreq\drive_HPULTRIUM3-SCSIHU10625WWRhcart3, from bptm.c.15753
NdmpSession: ndmp_public_session_destory: destroying session 0xe48df8
NdmpSession: [8] Received 16 (CONNECT_CLOSE_REPLY) ""
NdmpSession: [8] Replying error = 0
NdmpSession: NDMP SDK: stub called for missing shared library entry "ndmp_get_error_name"
NdmpSession: NDMP SDK: continuing without looking up error name; returning "?"
io_close: ignore ndmp close error, ?
drivename_write: Called with mode 1
drivename_unlock: unlocked
drivename_checklock: Called
drivename_lock: lock established
drivename_unlock: unlocked
drivename_close: Called
tpunmount: NOP: MEDIA_DONE 0 51707 0 DC1297 4000508 0
write_backup: write_data_tir failed. Sending exit status 84
send_brm_msg: EXIT dcnetapp3_1196768066 84
DeleteConnectionID: (-) Cleared Connection ID 0
emmlib_uninitialize: (0) Successfully released EMM session and database objects
bptm: EXITING with status 84

The ltid log file showed:
<4> IssueMount: Sending ROBOT_MOUNT request
<4> SendRobotReq: ROBOT_MOUNT request found
<4> SendRobotReq: Found drive name and path specified HPULTRIUM3-SCSIHU10625WWRhcart3: nrst7a dcnetapp3
<2> SendRobotReq: LTID - Sent ROBOTIC request, Type=1, Param2=5
<4> emmlib_UpdateMachineState: (0) Machine < dcback01 >, NetBackupVersion < 600000 >, MachineStateOpCode < 3 >
<4> emmlib_UpdateMachineState: (0) Machine < dcback01 >, Previous MachineStateBits < 14 >
<4> LtidProcCmd: Pid=5988, Data.Pid=5988, Type=204, Param1=3, Param2=0, LongParam=0
<6> DownDrivePath: DOWNing path nrst7a for HPULTRIUM3-SCSIHU10625WWRhcart3 on host dcback01
<6> WriteEntry: Updating drive HPULTRIUM3-SCSIHU10625WWRhcart3 serial number HU10625WWR at path nrst7a on attach host dcnetapp3
<2> update_drive: (0) Inputs: MediaServer = < dcback01 >, NdmpHost = < dcnetapp3 >, DriveName = < HPULTRIUM3-SCSIHU10625WWRhcart3 >, DrivePath = < nrst7a >
<16> update_drive: (0) UpdateDrive failed, emmError = 2005004, nbError = 0
<16> WriteEntry: (-) Translating EMM_ERROR_DriveAlreadyAllocated(2005004) to 258 in the device management context
<3> logstderrmsg: emmlib_UpdateDriveRuntime failed, status=258
<4> emmlib_UpdateMachineState: (0) Machine < dcback01 >, NetBackupVersion < 600000 >, MachineStateOpCode < 3 >
<4> emmlib_UpdateMachineState: (0) Machine < dcback01 >, Previous MachineStateBits < 14 >
<4> emmlib_UpdateMachineState: (0) Machine < dcback01 >, NetBackupVersion < 600000 >, MachineStateOpCode < 3 >
<4> emmlib_UpdateMachineState: (0) Machine < dcback01 >, Previous MachineStateBits < 14 >
<4> LtidProcCmd: Pid=5156, Data.Pid=5156, Type=54, Param1=3, Param2=5, LongParam=0
<2> ProcessRobotMsg: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=3, Param2=5
<4> ProcessRobotMsg: Sending robotic error 9 to BPTM

Solution:
Disabling Network Interface Card (NIC) Teaming on Media Server has been known to resolve this issue.

Supplemental Materials

SourceError Code
Value84
Descriptionmedia write error

Legacy ID



296586


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


Terms of use for this information are found in Legal Notices