Error message in Backup Exec 9.1

[Henrik_Jalse]

I changed tapes in our tape robot. But then the backup jobs stoped working regardles of the tape in use. This is the latest log:

Job Log for Normalbackup


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


Completed status: Failed Expand AllCollapse All
Job Information
Job server: CNCNET
Job name: Normalbackup
Job started: Tuesday, April 05, 2005 at 1:59:08 AM
Job type: Backup
Job Log: BEX00423.xml




Device and Media Information
Robotic Library Name: DELL 1
Drive Name: QUANTUM 1
Slot: 4
Media Label: Fredag 2
Media GUID: {E388588C-035F-4923-974E-703CBB2BCE83}
Overwrite Protected Until: 12/31/9999 12:00:00 AM
Appendable Until: 12/31/9999 12:00:00 AM
Targeted Media Set Name: Media Set 1




Job Operation - Backup
Backup Options
Media operation - overwrite.
Hardware compression enabled.





Server - \\CNCNET

Set Information - E: SystemLogg
Backup Set Information
Family Name: "Media created 4/5/2005 1:59:09 AM"
Backup of "E: SystemLogg"
Backup set #1 on storage media #1
Backup set description: "Normalbackup "
Backup Type: FULL - Back Up Files - Reset Archive Bit




Backup started on 4/5/2005 at 2:00:28 AM.
Backup completed on 4/5/2005 at 2:06:37 AM.

Backup Set Summary
Backed up 58 files in 4 directories.
Processed 3,521,604,980 bytes in 6 minutes and 9 seconds.
Throughput rate: 546 MB/min






Set Information - G: Data
Backup Set Information
Family Name: "Media created 4/5/2005 1:59:09 AM"
Backup of "G: Data"
Backup set #2 on storage media #1
Backup set description: "Normalbackup "
Backup Type: FULL - Back Up Files - Reset Archive Bit




Backup started on 4/5/2005 at 2:06:38 AM.

Backup Set Detail Information
Storage device "QUANTUM 1" reported an error on a request to write data to media.

Error reported:
Data error (cyclic redundancy check).




Backup completed on 4/5/2005 at 2:11:30 AM.

Backup Set Summary
Backed up 8438 files in 346 directories.
Processed 986,773,896 bytes in 4 minutes and 52 seconds.
Throughput rate: 193 MB/min










Tape Alerts
----- TapeAlert Events -----

Warning - A severe error occurred while reading or writing data. This job may not have been successfully completed.
Robotic Library: DELL 1
Drive: QUANTUM 1
Slot: 4

Critical - The tape is from a faulty batch or the tape drive is faulty:
1. Use a good tape to test the drive.
2. If the problem persists, call the tape drive supplier helpline.
Robotic Library: DELL 1
Drive: QUANTUM 1
Slot: 4




Job Completion Status
Job ended: Tuesday, April 05, 2005 at 2:22:05 AM
Completed status: Failed
Final error: 0x17 - Data error (cyclic redundancy check).

Final error category: Other Errors



Errors
Click an error below to locate it in the job log
Backup - G: DataStorage device "QUANTUM 1" reported an error on a request to write data to media.

Error reported:
Data error (cyclic redundancy check).

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

These tapes had worked fine before. What could be wrong?

Regards Henrik

[Amruta_Purandar]

Hello,

Cyclic redundancy check error is generic in nature and can be caused by numerous factors.
Please refer the following technote to troubleshoot the issue.
Title:
"Data error (cyclic redundancy check)" (00000017 HEX) is reported in the Backup Exec job log during a failed backup/verify operation
http://support.veritas.com/docs/192216

[Henrik_Jalse]

Hi!

The tape robot has run for a long time, the all of a sudden no jobs runs. Very strange. The tape drive is cleaned. No changes to scsi or tape driver configuration has been made. I will try with brand new tapes but i wonder if that will solve the problem.

Any other thoughts?

Regards Henrik

[Henrik_Jalse]

Hi!

I have tried with new tapes and the results are the same.
If I make I new smaller (about 1GB) job it works. But if i run the normal backup job it fails. I have also tried to make a new "normal backup job" but it also fails.

Any ideas?

Regards Henrik

[Sheetal_Risbood]

Hi,

Approx. how much data is being backed up in a single job ?

I would suggest you to divide the backup into 2-3 smaller jobs and check out the results.

Also, to isolate the cause of the issue, try taking the same backup on a B2D folder.

Please keep us updated on the progress of the case.

NOTE : If we do not receive your intimation within two business days, this post would be marked assumed answered and would be moved to answered threads pool.


Thanks.

[Sheetal_Risbood]

As per our previous reply, marking the case as assumed answered and moving it to answered questions pool.