Backup Still failing

[cjmelcher]

I submitted some info under the subjset Backup always failing, and asked if a backup could fail due to a dirty tape drive.

I cleaned my drive and got a failed backup. But go a new message at the end. Here it is.

Job operation: Verify

Storage device "Archive 0" reported an error on a request to seek to a logical media address.

Error reported:
Data error (cyclic redundancy check)
^^^^^

I think my stuff got backed up but just not verified. Any ideas on the message listed above will be appreciated.

Thank you
cjmelcher

 

[dellboy]

A CRC - cyclic redundancy check - is a networking thing were by a check is run once the data is sent if I am not mistaken, applying that theory it would suggest that a backup stlye CRC has failed, have you tried a test restore to see if any data is there?

Cheers

 

[cjmelcher]

I when into the event viewer and found some of these messages.

The device.\Device\Tape), has a bad block.

That is the tape correct or could the drive be failing?

Thanks for the help...

 

[Guest_imported]

The error message "Data error (cyclic redundancy check)" is reported in the Backup Exec for Windows NT v8.x log file and the backup/verify operation fails


TechNote ID: 192216 Last Updated: June 20 2002 10:59 AM GMT
Email this document to a colleague

Caution! The information in this TechNote is based upon certain assumptions, including product, operating system and platform versions. You can review this information in the
TechNote Summary portion of this document.
This document (192216) is provided subject to the disclaimer at the end of this document.


--------------------------------------------------------------------------------


Symptom:

The error message "Data error (cyclic redundancy check)" is reported in the Backup Exec for Windows NT v8.x log file and the backup/verify operation fails


Exact Error Message:

Storage device "[]" reported an error on a request to read/write data to/from media.

Solution:

The "Cyclic Redundancy Check" (CRC) error is generic in nature and can be caused by numerous factors. The following list contains the most common reasons for this error and potential ways to resolve the problem:

1. Contaminated read/write heads of the tape device.


Check with the hardware manufacturer for proper cleaning techniques.


2. Bad media.

Replace the media. Try a new tape that is certified by the hardware manufacturer.


3. Tape driver.

Load the appropriate Backup Exec tape driver.


4. SCSI controller wide negotiation enabled.

Use the manufacturer's SCSI setup program to disable wide negotiation on the SCSI controller card.


5. SCSI controller wide negotiation.

If the device is a wide (68 pin) SCSI device then wide negotiation may and should be used. If the device is narrow )50 pin) SCSI device, disable wide negotiation.


6. SCSI controller transfer rate is too fast.

Use the manufacturer's SCSI setup program to lower the SCSI transfer rate. Check with the controller and backup device manufacturer fir the proper configuration for SCSI transfer rate.


7. SCSI controller synchronous negotiation enabled.

Use the manufacturer's SCSI setup program to disable synchronous negotiation on the SCSI controller card. Check with the controller and backup device manufacturer fir the proper configuration for SCSI synchronous negotiation.


8. Incorrect termination or bad cables.

Verify the SCSI cable is good and for proper SCSI termination. DO NOT MIX Passive and Active termination.


9. Confirm the tape drive is functioning properly

Check with the tape drive manufacturer for diagnostic software to test the condition of the tape drive hardware.


10. General SCSI problems.

Isolate the tape drive on its own controller card.

 

[Grenage]

Normally when we have CRC issues we clean the drive, if that fails replace the tape - if you backup has been working fine for a good period of time this is probably your more likely solution.