Desktop

Ask something
Discussion Locked

Backup Exec and HP Ultrium 215

0 helpful
1 reply

by cmeisinger 3 views

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have an issue with my backups. First the backups suddenly quit working so I upgraded the firmware for the HP SureStore Ultrium 215. After doing that the backup seems to startup but then gets an error stating the drive needs to be cleaned. I cleaned the drive multiple times and used brand new cartridges but I am still receiving that message. I backup using Veritas Backup Exec version 8.5 on a Netware 5.1 machine.

Any help is much appreciated!

Chris

1 reply

by joseph moore

I found this article on Veritas website:
http://tinyurl.com/xscp

It talks about getting the following error when Backup Exec 7.5, 8.0 and/or 8.5 on Netware when using an HP SureStore tape drive:
"A hardware error has been detected during this operation. This
tape should not be used for any additional backup operations.
Data written to this tape prior to the error may still be restored.
SCSI bus timeout can be caused by a tape drive that needs
cleaning, a SCSI bus that is too long, incorrect SCSI
termination, or a faulty device. If the drive has been working
properly, clean the drive or replace the tape and retry the
operation.
Vendor: XXX
Product: XXX
ID: ??
Firmware: XXX
Function: Write(5)
Error: Timeout(1)
Sense Data:
00 00 00 00 - 00 00 00 00 - 00 00 00 00 - 00 00 00 00
00 00 00 00 - 00 00 00 00 - 00 00 00 00 - 00 00 00 00"

Basically, the article says that the SCSI type connected to the tape drive is the very high density cable interconnect (VHDCI) type. The fix is to buy an adapter to change to low density type.

Now, I use an IBM 3580 tape library and TSM, and my SCSI connections are all low density. Low density give you the ability to use longer cables. For me, my tape drive is 50 feet from my server, so I needed the longer cable length, hence the LD type.

Anyway, read the article and give it a shot.

hope this helps

This discussion is closed to new replies.