"E6300 Windows NT SCSI port error" in ARCserve Backup

Hi,

We use hp Storage Works 1/8 auto loader ultrium 448, ARCserve Backup r11.5 sp3, and Windows server 2003. We got "Windows NT SCSI port error" in ARCserve two times in two weeks recently. So the backup failed. I have to restart the auto loader first then restart the Windows server to fix it. That's painful. Please advice.

Thanks,
Wen
cdsglobalAsked:
Who is Participating?
 
dovidmichelConnect With a Mentor Commented:
The fact that it was necessary to restart the server to get it working again points to a bus level problem that resulted in a loss of communication to the tape device.

Typically a SCSI reset is sent to re-establish communication but it seems not in this case.

Still a lot of things can cause SCSI errors.
Check Event Viewer System log for errors from the controller at that point in time.
Configure HP Management Agents not to collect SCSI Information.
Update the
controller firmware and driver.
Try a new controller, cable, and terminator.
If there are any other devices on the bus move them to a different controller.
If the controller driver is Storport then they library and drive have to stay enabled, but if the SCSI Mini port controller driver is used, then disable the library and tape drive from within the OS Device Manager.
0
 
cdsglobalAuthor Commented:
Hi dovidmichel,

Thanks for you advice. We'll try to replace the cable and terminator first if SCIS errors happen again. We have ordered  the cable and terminator already. I'll let you know the result.

I am a little scared about update the controller firmware, because the SCIS controller also for the hard drives Array, if anything happened, the server will down, I can not afford it. So I'll try to replace the cable and terminator.

Thanks,
CDSglobal
0
 
dovidmichelCommented:
Some controllers support hard drives only,
some support both hard drives and tape drives but not at the same time
some support both at the same time.

HP has all three, so it is worth verifying this.
Regardless consider adding a controller just for the tape drive.
0
 
jjernstCommented:
Hi cdsglobal,

we're experiencing the exact same problem. This is not the first time this is happening. The last time it was a MS security update, which caused the error. It took HP 6 months to get us an update to fix the problem. We are removing the last MS updates and this will probably fix the problem.... I'll keep you posted
0
 
cdsglobalAuthor Commented:
I have replaced cable and terminator already one week, no problems so far. It looks like the problem is fixed. Thanks a lot for help,dovidmichel.

CDSGLOBAL
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.