V-79-57344-34028 - "Data error (cyclic redundancy check)" is reported in the Backup Exec job log during a failed backup/verify operation

Problem

"Data error (cyclic redundancy check)" is reported in the Backup Exec job log during a failed backup/verify operation on tape.
 

Error Message

0xe00084c7 - A backup storage read/write error has occurred. If the storage is tape based, this is usually caused by dirty read/write heads in the tape drive. Clean the tape drive, and then try the job again. If the problem persists, try a different tape. You may also need to check for problems with cables, termination, or other hardware issues. If the storage is disk based, check that the storage subsystem is functioning properly. Review any system logs or vendor specific logs associated with the storage to help determine the source of the problem. You may also want to check any vendor specific documentation for troubleshooting recommendations.

A backup storage read/write error has occurred. If the storage is tape based, this is usually caused by dirty read/write heads in the tape drive. Clean the tape drive, and then try the job again. If the problem persists, try a different tape. You may also need to check for problems with cables, termination, or other hardware issues. If the storage is disk based, check that the storage subsystem is functioning properly. Review any system logs or vendor specific logs associated with the storage to help determine the source of the problem. You may also want to check any vendor specific documentation for troubleshooting recommendations.

Final Error Code:  00000017 HEX 

Final Error Description:  "Data error (cyclic redundancy check)"

"Storage device "%Device%" reported an error on a request to write data to media. Error reported: Data error (cyclic redundancy check)." 

Error description:  "Data error (cyclic redundancy check)."

OR Job LogFinal Error Code:  a00084f9 HEX
 

Related Error Codes:

00000017 HEX
a000084f9 HEX
0xa000e006
0xe00084ec 
UMI code: V-79-57344-34028
UMI code: V-276-16
UMI code: V-79-57344-33991
UMI code: V-79-0-23
UMI Code: V-379-57665
 

Cause

The following list contains the most common reasons for this error:

1.  Contaminated read/write heads of the tape device:
2.  Bad media as there may be hard read/write errors :
3.  Tape driver:
4.  SCSI controller wide negotiation:
5.  SCSI controller transfer rate is too fast:
6.  SCSI controller synchronous negotiation enabled:
7.  Incorrect termination or bad cables:
8.  Confirm that the tape drive is functioning properly:
9.  General SCSI problems
10. Tape Drive / Tape Library Firmware issue.

If the backup is going to disk, the most common cause is an imminent drive failure.
Often, NTFS errors will start appearing in the event logs regarding bad blocks, disk, and CRC errors.
 

Solution

The cyclic redundancy check (CRC) error is generic in nature and can be caused by numerous factors.  Typically, this means that a tape read/write error has occurred. This is usually caused by dirty read/write heads in the tape drive. Clean the tape drive and try the job again. If the problem persists, consider trying a different tape. Finally, the problem could be with cabling, termination or other hardware issue."

The following list contains the most common reasons for this error and potential ways to resolve the problem:

If the error occurs when backing up to a Backup To Disk Location:

Run chkdsk on the source and destination drive to confirm the disk integrity.

If it occurs on deduplication storage: Confirm that the dedup folder is not running out of space on the volume where it resides.  If this is the case, attempt to follow the instructions found in: Reclaiming space in a Backup Exec Deduplication Folder - 100001882