11-16-2011 11:15 AM
I have several errors and events with Symantec Backup exec 11d Rev. 7170 on a Windows 2003 server (x86), I got an IBM Ultrium LTO 3 and I use LTO 3 tapes (400/800GB):
Not any job is finished, all of them end with failure, and when trying to restore I got another "hardware error occurred" error, I have installed hot fixes and I've even reinstalled BE services, I've deleted and reinstalled the drive (firmware too) as well as cleaned the drive but no success, my scsi cable seems to be ok (I've heard some suggestions to replace it),
I got these events 34114, 34113, 33152, 57665, 57600, this is my current config, if disable "Read SCSI pass-through" option I got the next error:
"the block size being used is incorrect" no matter the size I change the error is still the same.
Thanks in advance!!
11-16-2011 11:23 AM
http://www.symantec.com/docs/TECH66286
You may also need to check this for errors: Troubleshooting hardware with Backup Exec for Windows Servers using the SCSI Trace Utility (tracer.exe).
11-16-2011 05:28 PM
Try changing your blksize to match the buffer size. Read my article on how to tune your tape drive.
https://www-secure.symantec.com/connect/articles/tuning-my-lto4-tape-drive
Although it is written for LTO4, the techniques used are applicable for LTO3.
11-18-2011 11:02 AM
Thanks guys, I've run tracer.exe and all status success. I've been changing the block size as well as matching the buffer and the block size. I had "read scsi pass-through" enabled and I disabled it. The job was succesfully done but when trying to restore any files from the tape I get the "hardware error ocurred" events 34113 and 33152. I set the drive properties as:
blk size 64k
buffer size 64k
buffer count 10
high water count 7
and the next four options disabled
11-18-2011 04:53 PM
Are you restoring from an old backup or from a backup done with the above parameters? If it is the former, try a backup with the above parameters and then a restore. If it is the latter, then run the IBM diagnostic utility against the drive. Make sure that you stop all the BE services beforehand and select the write test.