Veritas 10 hw problems

[Kauko_Laine]

To somebody:

We have been having some problems trying to get our backup system running. Running backup failed allways with error:

from veritas backup exec:
"Storage device "HP 1" reported an error on a request to write data to media. Error reported: The request could not be performed because of an I/O device error.
V-79-57344-34029 - A hardware error occurred."

from system event log:
Event Type:Error
Event Source:halfinchVRTS
Event Category:None
Event ID:11
Description:
The driver detected a controller error on \Device\Tape0.

For more information, see Help and Support Center at

from application event log:
Event Type:Error
Event Source:Backup Exec
Event Category:None
Event ID:34113
Description:
Backup Exec Alert: Job Failed
(Server: "server") (Job: "Server-normal") Server-normal -- The job failed with the following error: A hardware error occurred.


Enviroment:
Intel server, new server
2* Intel Xeon 3.20 GHz, 4GB RAM
intel SCRU42X raid controller + 5 x SCSI hd
HP ultrium LTO 1 tapedevice, SCSI ID=2
Windows 2003 sp1 + updates up to date & Exchange 2003 sp1
Backup Exec 10.1 build 5629, + exchange agent; no updates available
LSI SCSI Adapter, integrated to mainboard, only Tape-device connected
(scsi speed reduced to 80Mb, tested also 320/160)


Tested:
scsi and tapedevice latest drivers (veritas and hp) and older ones

Add.info:
Remote Storage Services have been disabled on the server.


So, what to do?

[Tommi_Hellman]

Have you allready tryed diffrend scsi card setting:

Set the tape drive SCSI ID as low as possible, avoiding 0 or 1, which are usually reserved for bootable devices
Set INITIATE WIDE NEGOTIATION to off for controllers with a wide bus
Set INITIATE SYNC NEGOTIATION for the ID of the tape drive to off
Set MAXIMUM SYNC TRANSFER RATE to the slowest possible setting
DISCONNECT must be enabled for all tape drive SCSI IDs
Set SCSI PARITY CHECKING to off

WARNING: The Parity Checking adjustment is for diagnostic use only and should never be left disabled during production backups. Symantec Corporation cannot be held liable for data corruption due to Parity Checking being disabled.

[Christian_Borth]

Maybe these links could help you troubleshoot the system:

http://support.microsoft.com/?kbid=154690
http://seer.support.veritas.com/docs/237047.htm

[Kauko_Laine]

all these has done, w/o any good results.
I also test with HP tools about Tapestreamer healt. It was healthy. I believe that there are some problem betweenh Exchange 2003 programs and BE10.x. I have two similar servers, there Be10 works. Any other ideas?

[Deepali_Badave]

Hello,

The error "Storage device reported an error on a request to write data to
media" can usually be resolved by either erasing the media before running
the backup, or by replacing the media with new media.

The " CRC " or " Write data to Media " or " I/O device" errors can also
occur due to SCSI issues.
Please refer the following technotes and tips, which will help you resolve
the issue.

Tips:-
1) Clean tape drive atleast 3 to 4 times using cleaning media.
2) Download and update tape drive firmware from the manufacturers website.
3) Try using new media
4) Try taking a backup using the NTBACKUP utility and see the results.

NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.

[Kauko_Laine]

Thanks for advise.
The tapestreamer is new, as the whole server. Hp diagnostig tools did not find any problems with hw, even the stress test (4hours) was ok. Cleaning has made (total operation time of tapedevice is less than 10 hours) The new tapes works, but after one record the backup fails. Now also tested with erased tape = works. Are there any other solutions than use new tape or erased tape???

This is really strange error.