cancel
Showing results for 
Search instead for 
Did you mean: 

0x17 - Data error (cyclic redundancy check)

niketya
Not applicable
Has anyone received this error message? If so did anyone managed to find a solution. I did confirm the revision numbers on the server that is running the back up and on the server that is running the remote agent.
3 REPLIES 3

Ken_Putnam
Level 6
See http://seer.support.veritas.com/docs/199542.htm for the Veritas CRC error troubleshooting guide.

Ameet_Thakkar
Level 6
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) This error usually occurs due to hardware or SCSI related issues.

Perform the following steps, which will help in resolving the issue.

1. Ensure that the device is properly terminated.
2. Clean the device used. Refer to the manufacturer manual for cleaning instructions.
3. Update the firmware of the tape devices used to the latest.
4. Ensure that SCSI controller drivers are updated to the latest 5. Try using NTBACKUP for backing up data.
Note: Stop all the Backup Exec services and before performing NTBACKUP operation.
Also let us know the results of the test using NTBACKUP.
We would suggest you please refer to the following technote, which will give you possible solution to the problem that you are facing.
http://seer.support.veritas.com/docs/192216.htm

6. To isolate the problem, try performing backup on a Backup-to-disk folder.
Please carry out backup operation on Backup to disk folder and let us know if you come across the same errors .
For more information on Backup to Disk folder, you may refer to Administrator's Guide VERITAS Backup Exec (tm) 9.1 for Windows Servers Administrator's Guide (English) http://seer.support.veritas.com/docs/266190.htm

( Refer from page number- 149, Using Backup to Disk folders and files )
b) Try using NTBACKUP for backing up data.
Note: Stop all the Backup Exec services and before performing NTBACKUP operation.
Also let us know the results of the test using NTBACKUP.
-----------------------------------------------------------------------------------------------------
In addition to the above steps please refer to the following steps as well.
Uninstall the existing device drivers and reinstall the latest Veritas drivers. Run tapeinst.exe to install Veritas driver.
"TAPEINST.EXE" is located in the directory x:\Program Files\VERITAS\Backup Exec\NT (TAPEINST.EXE" is an automated installation application for installing tape device drivers ) http://seer.support.veritas.com/docs/199881.htm

Download device drivers from the following link.

VERITAS Backup Exec (tm) 9.1 - Device Driver Installer (20050115) - Includes Tape Driver Release (20041231) and Robotic Library Release (45) (Intel Only)


http://seer.support.veritas.com/docs/273853.htm

Title:- VERITAS Backup Exec (tm) 10.0 - Device Driver Installer (20050115) - Includes Tape Driver Release (20041231) and Robotic Library Release (45) (Intel Only)

http://seer.support.veritas.com/docs/273887.htm




Also refer the following technote :-
http://seer.support.veritas.com/docs/245177.htm

We hope this helps.

BIGmag
Not applicable
I use a job Monday to Friday.
Within the week, the backup runs without any problems.
On Friday I always get a "Ox17 CRC-Failure"
Meanwhile I unchecked the box for the "Write checksum on media", "Verify after backup" - without effect.
I've tried different tapes, changed the backup-day from friday to saturday - without success.
The backup-admin has no restrictions.
The revision number on the mediaserver is 9.1 4691 and on the remote server 9.1 4691.14

I don't understand, why it works four days and one day I have these troubles!