error bad data

[thomasholmes]

I have been succcessfully using BackUp Assist for over a year.
Lately I am getting the dreaded "Error Bad Data" message on a request to write data to media and during the Verify process during a request to read data from media.
see error log below for details.
does not happen every day, happens sometimes two days in a row. I use a different tape each day, m-f with 10 tape rotation.

seems to be on Drive E which is my second internal hard drive

I have cleaned the tape drive. I can create new media; and do so upon getting the error. I can do a test back up.

thanks in advance for a reply.

thomas

. LaBackup Status
Operation: Backup
Active backup destination: 4mm DDS
Media name: "Monday (2/5/2007 10:16 Seq452)"

Backup of "C: "
Backup set #1 on media #1
Backup description: "Set created 2/5/2007 at 10:16 AM"
Backup Type: Normal

Backup started on 2/5/2007 at 10:19 AM.
Warning: The file \Accounting\MSSQL\Data\GPSDYNAMICSDat.mdf in use - skipped.
Warning: The file \Accounting\MSSQL\Data\GPSSNIDat.mdf in use - skipped.
Warning: The file \Accounting\MSSQL\Data\master.mdf in use - skipped.
Warning: The file \Accounting\MSSQL\Data\mastlog.ldf in use - skipped.
Warning: The file \Accounting\MSSQL\Data\model.mdf in use - skipped.
Warning: The file \Accounting\MSSQL\Data\modellog.ldf in use - skipped.
Warning: The file \Accounting\MSSQL\Data\msdbdata.mdf in use - skipped.
Warning: The file \Accounting\MSSQL\Data\msdblog.ldf in use - skipped.
Warning: The file \Accounting\MSSQL\Data\northwnd.ldf in use - skipped.
Warning: The file \Accounting\MSSQL\Data\northwnd.mdf in use - skipped.
Warning: The file \Accounting\MSSQL\Data\pubs.mdf in use - skipped.
Warning: The file \Accounting\MSSQL\Data\pubs_log.ldf in use - skipped.
Warning: The file \Accounting\MSSQL\Data\tempdb.mdf in use - skipped.
Warning: The file \Accounting\MSSQL\Data\templog.ldf in use - skipped.
Warning: The file \Accounting\MSSQL\LOG\ERRORLOG in use - skipped.
Warning: The file \Accounting\MSSQL\LOG\GPSDYNAMICSLog.ldf in use - skipped.
Warning: The file \Accounting\MSSQL\LOG\GPSSNILog.ldf in use - skipped.
Warning: The file \Accounting\MSSQL\LOG\SQLAGENT.OUT in use - skipped.
Warning: The file \Inetpub\nntpfile\article.hsh in use - skipped.
Warning: The file \Inetpub\nntpfile\group.lst in use - skipped.
Warning: The file \Inetpub\nntpfile\groupvar.lst in use - skipped.
Warning: The file \Inetpub\nntpfile\history.hsh in use - skipped.
Warning: The file \Inetpub\nntpfile\xover.hsh in use - skipped.
Warning: The file \Inetpub\nntpfile\root\group.vpp in use - skipped.
Warning: The file \Inetpub\nntpfile\root\_slavegroup\group.vpp in use - skipped.
Warning: The file \Inetpub\nntpfile\root\control\group.vpp in use - skipped.
Backup completed on 2/5/2007 at 10:34 AM.
Directories: 280
Files: 3586
Skipped: 26
Bytes: 1,107,270,156
Time: 14 minutes and 38 seconds
Media name: "Monday (2/5/2007 10:16 Seq452)"

Backup of "E: Vol2"
Backup set #2 on media #1
Backup description: "Set created 2/5/2007 at 10:16 AM"
Backup Type: Normal

Backup started on 2/5/2007 at 10:34 AM.
Warning: The file \Database\Backend.ldb in use - skipped.
Warning: The file \Database\Backend.mdb in use - skipped.
Warning: The file \Database\MILLAGE\2006 lists and tally.xls in use - skipped.
Warning: The file \Database\MILLAGE\06 Millage Files\all clients service 2006.xls in use - skipped.
Warning: The file \Database\RefugeeToolkit\RefugeeBackend.ldb in use - skipped.
Warning: The file \Database\RefugeeToolkit\RefugeeBackend.mdb in use - skipped.
Warning: The file \Users\carolboerkoel\FAMILY REUNION.xls in use - skipped.
Warning: The file \Users\ctyler\My Documents\SNI Interpretation.doc in use - skipped.
Warning: The file \Users\ctyler\My Documents\~WRL0001.tmp in use - skipped.
Warning: The file \Users\ctyler\My Documents\~WRL0005.tmp in use - skipped.
Warning: The file \Users\ctyler\My Documents\~WRL1344.tmp in use - skipped.
Warning: The file \Users\ctyler\My Documents\~WRL3904.tmp in use - skipped.
Warning: The file \Users\toosterbaan\CM Procedures\Services and Programs\4.8 Fan Giveaway.doc in use - skipped.

Error: The device reported an error on a request to write data to media.
Error reported: Bad data.

Backup completed on 2/5/2007 at 1:40 PM.
Directories: 3308
Files: 37271
Skipped: 13
Bytes: 14,770,883,900
Time: 3 hours, 6 minutes, and 32 seconds

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

Verify Status
Operation: Verify After Backup
Active backup destination: 4mm DDS

Verify of "C:"
Backup set #1 on media #1
Backup description: "Set created 2/5/2007 at 10:16 AM"
Verify started on 2/5/2007 at 1:42 PM.
Verify completed on 2/5/2007 at 1:58 PM.
Directories: 280
Files: 3586
Different: 0
Bytes: 1,107,270,156
Time: 15 minutes and 46 seconds

Verify of "E:"
Backup set #2 on media #1
Backup description: "Set created 2/5/2007 at 10:16 AM"
Verify started on 2/5/2007 at 1:58 PM.

Error: The device reported an error on a request to read data from media.
Error reported: Bad data.

Verify completed on 2/5/2007 at 3:40 PM.
Directories: 2134
Files: 19503
Different: 0
Bytes: 11,000,771,156
Time: 1 hour, 41 minutes, and 50 seconds

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

[Dhiraj]

Hi Thomasholmes,

Thanks for posting on our forums.

This is Raj from BackupAssist technical support.

Typically, when I have encountered the error located within your backup reports it has related to a problem with the actual hardware device itself.

You could run some tests to help determine this.

1. Enable debugging logging (View > Navigator > Information)
2. Create a new backup job (View > Navigator > backup jobs) and set it up in the Options tab to backup to File instead of Tape. Select a the same set of files to backup in the Files&Dirs tab as your original job.
3. Run a test backup of this job from the Tools tab.
4. Now change this job to backup to Tape instead of File and run the same test with a tape that has failed previously.
5. Now run this test again with a brand new tape (preferably one that has never been used).

Additionally, can you please check the Windows Event Viewer (Start > Run > eventvwr) to determine if there are any hardware related errors with this backup error. In the past, I've noted Event ID 7, Bad Block errors and Event ID 9, timeout errors.

I would also suggest tying the following if the backup to file works, but the tape backup does not:

a) Run a cleaning tape through the tape drive 4 or 5 times
b) Run any tape drive diagnostic tools you may have - should be supplied by the tape drive manufacturer - to test the validity of the drive.
c) Ensure that you have the latest drivers/firmware for your tape drive and controller devices (SCSI card)
d) Check the cabling, SCSI termination, etc
e) Try new tape media if none of the above helps
f) Try either replacing the SCSI controller or have the tape drive serviced

You might also want try suspending any virus scan or other security software while the backup is running, and avoiding the use of CPU intensive programs during the backup should any be running.

I hope the above suggestions help in resolving the issue you are facing, but in case it doesn't could you please enable debugging logging (View > Navigator > Information) and resimulate the error and then supply me with some diagnostic information - for help with compiling the diagnostics, please visit: http://www.backupassist.com/HTMLHelp/Tr ... upport.htm and send the diagnostics.zip file to support @ backupassist . com.

[Adain21]

Thanks for taking the time to help, I really apprciate it.