cyclic redundancy check?

[prha]

Last night my back up failed. I have not changed any setting,
I am running NT4 server. with BE 7.3
Looking at the log file the job appears to have been done except that at the end there is the following message
Storage device "hp 0" reported an error on a request to read data from media
Error reported:
Data error (cyclic redundancy check)
Does anyone know what this means?
the only difference I can see is that the back up took 2 hours less than usual.
I found a couple of corrupt emails so I will delete these, I will also give the DAT drives a clean and see what happens tomorrow but if anyone knows what would suddenly cause this any advie would be greatly appreciated

 

[SQLBill]

Check out thread183-483753

-SQLBill

 

[prha]

Thanks for that SQLBill,

I have cleaned the drive and will see if I get the message again next week when I use the tape again. It did happen during the verify so it looks like the job was OK.
However I am slightly concerned with the fact that the back up took 2 hours less than usual?

Any clues?

 

[SQLBill]

I'm thinking that the error causes it to skip the verification. That would make the backup time shorter. But that's only my guess, I've never seen this error myself and haven't seen anything on it except for the thread I referenced.

-SQLBill

 

[Fuubar]

Errors like yours during verify indicate a hardware problem occurred pertaining to the read heads in the tape drive.
-Check error statistics for the tape drive by going into Properties|Statistics tab on the drive.

-Clean tape drive twice w/new cleaning cartridge or whatever method you use to clean that particular drive.

-Check the same statistics for the tape that error occurred on. Maybe a new tape is in order.

-If the errors persist, close BE, stop all BE services and set them to Manual so they don't restart. Then run tapeinst.exe in \Program Files\Veritas\Backup Exec\NT to remove all Veritas drivers. Load MS or vendor drivers and test some backups using NTBackup and make sure you specify a Verify as it is not selected by default in NTBackup. If the verify bombs out w/NTBackup as well, get the log and you now have ammunition when you contact the hardware manufacturer for repair/replacement. (Thats what I did.)

Good luck!

 

[prha]

Thanks for all the advice, will keep this on hand. I cleaned the drives a couple of times and the back up worked last night no problems.

Cheers