Coninuos 84 errors NetBackup 5.1

[joshluigp]

hello!

i need help.!! :)

I have a master server with netbackupp 5.1 and i installed MP6 with L180 library with 3 drives assigned. And when i made a backup from many raw devices i recived 84 errors.

the policy was created to backup 103 disks 33Gb each one from dmx3000 using que emcp trayectory. The policy are configure like this.

12 jobs per policy

media multiplexing 6

and the Backup selection are something like these.

NEW_STREAM
/devices/pseudo/emcp@80:h,raw
NEW_STREAM
/devices/pseudo/emcp@81:h,raw
NEW_STREAM
/devices/pseudo/emcp@82:h,raw
NEW_STREAM
/devices/pseudo/emcp@83:h,raw
NEW_STREAM
/devices/pseudo/emcp@84:h,raw
NEW_STREAM
/devices/pseudo/emcp@85:h,raw
NEW_STREAM
/devices/pseudo/emcp@86:h,raw
NEW_STREAM
/devices/pseudo/emcp@87:h,raw
NEW_STREAM

the OS is Solaris 5.9 .

 and the logs form de OS looks like these.

Aug  9 03:39:20 backup01 scsi: [ID 107833 kern.notice]  Sense Key: Media Error
Aug  9 03:39:20 backup01 scsi: [ID 107833 kern.notice]  ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
Aug  9 08:15:13 backup01 scsi: [ID 107833 kern.warning] WARNING: /pci@15d,700000/scsi@1/st@1,0 (st57):
Aug  9 08:15:13 backup01        Error for Command: write                   Error Level: Fatal
Aug  9 08:15:13 backup01 scsi: [ID 107833 kern.notice]  Requested Block: 1836866                   Error Block: 1836866
Aug  9 08:15:13 backup01 scsi: [ID 107833 kern.notice]  Vendor: SEAGATE   

I hope anyone can help me.

Thanks

Regards.!!

Message Edited by joshlui on 08-09-200709:47 AM

[Omar_Villa]

Hi,

   Normaly status 84 are hardware problems, have you clean all your drives? did you check that every 84 error wasnt over the same media? some times a bad media can give you all this, also you can try to follow the In-depth status 84 troubleshooting guide on http://seer.support.veritas.com/docs/278565.htm.

Hope this helps.

Regards

[Omar_Villa]

Aug  9 08:15:13 backup01 scsi: [ID 107833 kern.warning] WARNING: /pci@15d,700000/scsi@1/st@1,0 (st57):
Aug  9 08:15:13 backup01        Error for Command: write                   Error Level: Fatal

Other thing that I see on the logs you provide is that maybe you have an HBA issue, try to reset the HBA and ensure that the SAN switch is able to see the corrects WWN's if not you will need to re-zone them.

Regards 

[joshluigp]

Hello,!!

I clean drivers frecuently but the error is not on all policies, it´s just appear when i do these kind of backups.

On backups that didn´t take much time the backup made without errros. But these backups take aprox 2:40 hrs pear pool of disks and the error 84 appear sometimes.

The storage is connected DA. i don´t have any switch between server and storage.

And the most anormal is that did´nt appear always.  sometimes one pool of disks made the backup correctly and the next pool of discs the error appear.

This error happened with diferent medias. this the bptm log.

03:02:48.353 [15099] <2> write_data: received first buffer (65536 bytes), begin writing data
03:39:20.912 [14832] <2> send_brm_msg: MEDIA NOT READY
03:39:20.912 [14832] <2> write_data: attempting write error recovery, err = 5
03:39:20.912 [14832] <2> tape_error_rec: error recovery to block 7349881 requested
03:39:20.913 [14832] <2> tape_error_rec: attempting error recovery, delay 3 minutes before next attempt, tries left = 5
03:42:20.892 [14832] <2> io_ioctl: command (0)MTWEOF 0 from (overwrite.c.489) on drive index 4
03:42:20.892 [14832] <2> io_ioctl: MTWEOF failed during error recovery, I/O error
03:42:20.895 [14832] <2> tape_error_rec: absolute block position after error is 7346343
03:42:20.895 [14832] <2> set_job_details: Done
03:42:20.913 [14832] <16> write_data: cannot write image to media id DWH046, drive index 4, I/O error
03:42:20.925 [14832] <2> log_media_error: successfully wrote to error file - 08/09/07 03:42:20 DWH046 4 WRITE_ERROR
03:42:20.925 [14832] <2> check_error_history: called from bptm line 17599, EXIT_Status = 84
03:42:20.925 [14832] <2> check_error_history: using time window of 24 hours
03:42:20.925 [14832] <2> check_error_history: using drive error threshold of 20
03:42:20.947 [14832] <2> check_error_history: drive index = 4, media id = DWH046, time = 08/09/07 03:42:20, both_match = 0, m
edia_match = 0, drive_match = 2
03:42:20.947 [14832] <2> io_close: closing /usr/openv/netbackup/db/media/tpreq/DWH046, from bptm.c.15695
03:42:20.948 [14832] <2> tpunmount: Check_for_waiting = 0, No_tpunmount_after_restore = 0, Media_Unmount_Delay = 0, MediaOffs
et = 33
03:42:20.948 [14832] <2> tpunmount: tpunmount'ing /usr/openv/netbackup/db/media/tpreq/DWH046
03:42:20.949 [14832] <2> TpUnmountWrapper: SCSI RELEASE
03:42:31.927 [14832] <2> send_brm_msg: ERROR 84
03:42:43.920 [14832] <2> mpx_terminate_exit: EXITING with status 84

Thanks.

Regards,!!