Backup Exec Error the Media is bad 

Job ended: dinsdag 15 januari 2008 at 0:35:07
Completed status: Failed
Final error: 0xe00084c7 - The media is bad.
Final error category: Backup Media Errors

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


 



Storage device "HP 1" reported an error on a request to read data from media. Error reported: Data error (cyclic redundancy check). This could be caused by either a dirty tape drive, bad media, or a SCSI problem.V-79-57344-33991 - The media is bad.


The above message I got 2 consequitve times from backup exec.


I used a cleaning tape to clean the heads.


I used Quantum Software to verify my backupunit (HP VS80) and all was ok.


But I still received the same error message.

 



Document ID: 192130

http://support.veritas.com/docs/192130



The error message "Bad Data" is reported by Backup Exec during backup or verify operations.





Exact Error Message

Backup Exec reported an error on a request to (read/write) data (to/from) storage media. Error reported: Bad Data



Details:



The "Bad Data" error is generic in nature and can be caused by many factors. The following list contains the most common reasons for this error and potential solutions:

1.  Contaminated read/write heads of the tape device. Running 3-4 consecutive cleaning cycles will usually resolve this problem.


2.  Bad media.  
3.  Tape head alignment problems. This would require replacing the tape device.


4.  SCSI transfer rate to the tape device is too fast. Use the manufacturer's SCSI setup program to lower the transfer rate.


5.  Disable the sync negotiation to the tape device in the SCSI setup program.


6.  Check/replace the SCSI cable or terminator.


7.  Isolate the tape drive on its own controller card.



 



The first item did it. just run the clean tape 3/4 times and now my backup works again.

Comments

Post a Comment

Popular posts from this blog

Exchange Server Error -1018: How Microsoft IT Recovers Damaged Exchange Databases

Image
I found this paper on the showcase site from microsoft I hope it is of help to you. It sure helped me!     Technical White Paper Published: August 1, 2005 Executive Summary Error –1018 (JET_errReadVerifyFailure) is a familiar—and dreaded—error in Microsoft® Exchange Server. It indicates that an Exchange database file has been damaged by a failure or problem in the underlying file system or hardware. This paper explains the conditions that result in error –1018. It also covers the detection mechanisms that Exchange uses to discover and recover from damage to its database files. The Microsoft Information Technology group (Microsoft IT) runs one of the most extensive Exchange Server organizations in the world. Exchange administrators at Microsoft have investigated and recovered from dozens of –1018 error problems. This paper shows you how Microsoft IT mo...
Read more

[Solved] The Group Policy client-side extension Internet Explorer Zonemapping failed to execute

Image
I had the error below in my application eventlog.     Event Type:    Error Event Source:    Userenv Event Category:    None Event ID:    1085 Date:        30-09-2008 Time:        15:20:30 User:        NT AUTHORITY\SYSTEM Computer:    TBG-TS01 Description: The Group Policy client-side extension Internet Explorer Zonemapping failed to execute. Please look for any errors reported earlier by that extension. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp .   My problem was with my site to zone assignment list I used a wildcard like this: “ *microsoft.com ” but what you need to do is this “ *.microsoft.com ” So it is safe to say that the documentation from microsoft needs some sort of an update stating that y...
Read more

How to Uninstall WSUS 3.0 after you have (removed/fucked up) the database manually

Well if somehow your wsus 3.0 database becomes corrupt. Due to an Database administrator removing the instance for example. I tried to remove through the Add/Remove programs dialog but all I got back was. Event Type: Information Event Source: MsiInstaller Event Category: None Event ID: 11725 Date: 25-09-2007 Time: 11:17:18 User: Domain\Administrator Computer: WSUSSERVER Description: Product: Microsoft Windows Server Update Services 3.0 -- Removal failed. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 7b 32 43 30 44 37 45 33 {2C0D7E3 0008: 35 2d 45 45 36 45 2d 34 5-EE6E-4 0010: 44 43 37 2d 42 41 31 33 DC7-BA13 0018: 2d 32 43 36 38 41 45 44 -2C68AED 0020: 45 42 35 39 44 7d EB59D} And voila the program was removed from the ADD/Remove Programs dialog. So I had nothing. Inspecting the Wsus installation log at %temp%\wsus*.log Reveals the following: MSI (s) (8C:74) [11:17:38:402]: Product: Microsoft Windows Serve...
Read more