Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrade.
Please accept our apologies in advance for any inconvenience this might cause.

Disk backup getting error "Tape read/write error has occurred."

Created: 28 Feb 2013 | 1 comment

My environment consists of a Windows 2003 SBS 32 bit server on which Backup Exec 12.5 is loaded.  I also have BE Client on a Windows 2003 64 Bit server used as a Terminal Server.  All backups are made to USB drives attached to the SBS server.  I perform a full backup each day starting at 10 PM and usually finishing around 8 AM.  I have had this setup for years with minimal problems but for the past several months I have been getting an error, usually during the verify process with the following message:

"Job ended: Thursday, February 28, 2013 at 6:09:41 AM

Completed status: Failed

Final error: 0x300084c7 - 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 then try the job again.  If the problem persists, try a different tape.  You may need to check for problems with cables, termination, or other hardware issues.  Final error category: Backup Media Errors

For additional information regarding this error refer to link V-79-57344-33991 "

All five of my backup drives are 1.8 Tb Transcend drives used only for backup and the backup is about 380 Gb and overwrites previous data, so there is a lot of space left.  I have run defrag on the disk and chkdsk has found no problem.  I sometimes am able to go 2 or 3 weeks without an error, but that is about it. Are there any suggestions short of replacing that individual drive?  

Operating Systems:

Comments 1 CommentJump to latest comment

Sush...'s picture

Hello there,

   Please refer to the following technote

http://www.symantec.com/docs/TECH5433 : "Data error (cyclic redundancy check)" is reported in the Backup Exec job log during a failed backup/verify operation

 

Here is an abstract from the above technote:

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.

 

Thanks,

-Sush...

Hope this piece of Information Helps you... and if it does then mark this response as Solution....!!!