Data error (cyclic redundancy check)Using Veritas 9.1

Posted on 2006-06-06
Medium Priority
Last Modified: 2013-12-01
Hello Guys,

I am having an issue with one of our clients using Veritas 9.1 running on SBS 2003, The problem is that it keeps failing every now and then with a 0x17 Data error (cyclic redundancy check).

We have looked through the Veritas/symantec website and found a whole bunch of suggestions so we have done the following:

Changed the tape drive
Changed the scsi contoller
Changed the tapes
Changed the scsi cable

And still we are getting this problem, even more strangely when the backup fails with a "CRC" error the job history some how deletes itself, but does not log anything in the event log about the job history deleting???

Can anyone help?
Question by:Adrissupport
LVL 88

Accepted Solution

rindi earned 1000 total points
ID: 16840793
Is the SCSI controller for the tape drive separate from the HD controller? Are the Disks still good? Run a chkdsk /x on them (do that after hours, as it can take a long time on large disks, and needs to run while windows is booting. Also check the terminator is good, and of course you need all the servicepacks and updates of veritas.

Assisted Solution

mrwaqar earned 1000 total points
ID: 16840814
It is most probably because of faulty media. Please make sure the 2nd Tape you tried was a working one. You also can try using ntbackup for a test backup. And to make double sure try with one NEW media if possible.

Good Luck!

Author Comment

ID: 16840833
Cheers Guys for your prompt response, The Scsi controller is seperate from the HDD's because we thought that could of been the problem, I also checked the terminators when I was there.

With regards to the other answer, These are brand new tapes that it is failing on, it failed on old tapes so we got him to replace all tapes with brand new ones.

I will have to use the windows backup to see if it works on that.

LVL 11

Expert Comment

ID: 16844824
Try making backups with the Windows backup tool for a week or two.  I've seen this happen with Veritas (was happening here at the zoo when I first started) when too much data is changed on the system during the backup.  It seems like it overwhelms the buffer in Veritas, or something, causing the error.  The Windows shadow copy seems to deal with this better, as counter-intuitive as that sounds.

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Is your phone running out of space to hold pictures?  This article will show you quick tips on how to solve this problem.
Article by: evilrix
Looking for a way to avoid searching through large data sets for data that doesn't exist? A Bloom Filter might be what you need. This data structure is a probabilistic filter that allows you to avoid unnecessary searches when you know the data defin…
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…
This Micro Tutorial will teach you how to reformat your flash drive. Sometimes your flash drive may have issues carrying files so this will completely restore it to manufacturing settings. Make sure to backup all files before reformatting. This w…
Suggested Courses

807 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question