Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

Failed full backup v.10d

Created: 20 Feb 2011 • Updated: 30 Jun 2011 | 14 comments
This issue has been solved. See solution.

Hello.  I am having problems with my MS2003 BE10d running a full backup to tape (Quantum LTO-4).  I have been able to run diff backups just fine but when I try a full backup I get errors.  I have cleaned the heads, tried new media, move media to scratch, with no sucess.  I am not sure what is wrong and I am a bit of a novice with this setup (inherited it).  I have read about updating the device drivers but not sure how to determine which ones to try to update to.  Here are the app and sys logs in regard to the backup job error.  I welcome any assistance.  Tnx in advance.

SOFTWARE--------------------------------

Event Type:    Error
Event Source:    Backup Exec
Event Category:    Devices
Event ID:    33152
Date:        2/18/2011
Time:        10:50:04 PM
User:        N/A
Computer:    IMM-SRV-01
Description:
Adamm Mover Error: Write Failure!
Error = ERROR_CRC
Drive = "QUANTUM 1"
    {D447B0F9-6F69-47C4-9499-FD962E06857A}
Media = "#DD82A077-000"
    {DD82A077-C8D3-4A11-93F2-A3D90950441C}
Read Mode: SingleBlock(0), ScsiPass(0)
Write Mode: SingleBlock(0), ScsiPass(0)
Data:
0000: 00 00 00 00 00 00 00 00   ........
0008: 00 00 00 00 00 00         ......  

Event Type:    Error
Event Source:    Backup Exec
Event Category:    None
Event ID:    57665
Date:        2/18/2011
Time:        10:50:49 PM
User:        N/A
Computer:    IMM-SRV-01
Description:
Storage device "QUANTUM 1" reported an error on a request to write data to media.

Error reported:
Data error (cyclic redundancy check).
This could be caused by either a dirty tape drive, bad media, or a SCSI problem..

 For more information, click the following link:
http://eventlookup.veritas.com/eventlookup/EventLo...
Data:
0000: 17 00 00 00 ec 84 00 e0   ....ì?.à
0008: 00 80 00 00 00 00 00 00   .?......
0010: 93 03 00 00               ?...    

Event Type:    Error
Event Source:    Backup Exec
Event Category:    None
Event ID:    34113
Date:        2/18/2011
Time:        10:53:28 PM
User:        N/A
Computer:    IMM-SRV-01
Description:
Backup Exec Alert: Job Failed
(Server: "IMM-SRV-01") (Job: "Full Backup") Full Backup -- The job failed with the following error: Error reading/writing data from/to the media.

Event Type:    Error
Event Source:    QLTOx32
Event Category:    None
Event ID:    7
Date:        2/18/2011
Time:        10:50:04 PM
User:        N/A
Computer:    IMM-SRV-01
Description:
The device, \Device\Tape0, has a bad block.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 04 00 68 00 01 00 c0 00   ..h...À.
0008: 00 00 00 00 07 00 04 c0   .......À
0010: 00 01 00 00 9c 00 00 c0   ....?..À
0018: 00 00 00 00 00 00 00 00   ........
0020: 00 00 00 00 00 00 00 00   ........
0028: 51 81 4b 03 00 00 00 00   QK.....
0030: ff ff ff ff 00 00 00 00   ÿÿÿÿ....
0038: 40 00 00 c4 02 00 00 00   @..Ä....
0040: fe 20 06 12 80 00 00 00   þ ..?...
0048: 00 80 00 00 84 03 00 00   .?..?...
0050: 00 00 6e 02 30 f0 19 87   ..n.0ð.?
0058: 00 00 00 00 20 1b b9 86   .... .¹?
0060: 00 00 00 00 00 00 00 00   ........
0068: 0a 01 00 00 20 00 00 00   .... ...
0070: 00 00 00 00 20 70 24 86   .... p$?
0078: 70 00 03 00 00 00 00 1e   p.......
0080: 00 00 00 00 0c 00 00 00   ........
0088: 00 95 00 00 00 00 00 00   .?......

Comments 14 CommentsJump to latest comment

pkh's picture

If the tape drive requests to be cleaned despite being recently cleanse, then it is most probably faulty and needs to be replaced.  To verify that the hardware is faulty, you can use the manufacturer's diagnostic program to test it.  Make sure you stop all the BE services before the test and that you select the write test.

ksdst1's picture

Hi pkh...tnx for the reply.  I cleaned the drive twice, updated the device drivers and ran the test.  Results show one error but not sure what it means.  thoughts? 

Test Summary
    Drive Detection Test -------- : Passed
    SCSI Interconnect Test ------ : Passed
    Pre Test Log Page 7 --------- : Skipped
    Tape Load Test -------------- : Passed
    Quick Write/Read Test ------- : Passed
    Small Buffer Wr/Rd Test ----- : Passed
    System Level Test ----------- : Passed
    Time Test ------------------- : Passed
    Multi-Pattern Test ---------- : Passed
    LTO Error Rate Test  -------- : Failed
    Collect Log Page 7 ---------- : Skipped
Problem Detected
 

pkh's picture

I suggest that you check the error with the drive manufacturer.

If your tapes are quite old and their statistics show a lot of errors, you might want to replace them.

ksdst1's picture

Hello....my last full backup was successful but last night when I tried the next full backup it failed with the error messages in the attached word file.  I was running differential backups just fine since the last full backup. 

I will clean the drive and run the manufacturer utiliity software again as before.  But as I inherited this setup I'd like to check everything from scratch.  I read that it is favorable to install BE device drivers and for my version 10d / Quantum LTO-4 drive and BE lists "BackupExecTapeDeviceDriverInstall20061015_285593.exe" as the drivers.  However, when i go to the "supported drives" list my drive is not listed.  The W2003 server system is currently using the manufacturer driver QLTOx32.  Is it advised to install the BE driver instead or use the manufacturers?

Thanks...

ksdst1's picture

Well I have updated the device firmware and have the latest OEM drivers (drive seemed to be working for full backups and definitely no probs with differentials before).  I used OEM xTalk test utility with one error "LTO Error Rate Test Failed".  Possible cause could be bad head or bad batch of new tapes.  Hmm.  Curious but maybe not important, in the addamlog all drive info is good but one line "Device Type 0, "***" which maybe due to OEM drivers and not BE drivers??  W2003 Sys Lob errors are most troubling with Event ID: 7, Device\Tape ) has a bad block (below).

At this point i am not sure if this all points to a BE software interface issue, a hardware/bad drive issue or something else like scsi connections, other driver, etc.  Not sure how to troubleshoot further or how to interpret the "data" part of the error msg below.   Any ideas on this matter would be much appreciated!!

Event Type:    Error
Event Source:    QLTOx32
Event Category:    None
Event ID:    7
Date:        3/25/2011
Time:        11:59:19 AM
User:        N/A
Computer:    IMM-SRV-01
Description:
The device, \Device\Tape0, has a bad block.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 04 00 68 00 01 00 c0 00   ..h...À.
0008: 00 00 00 00 07 00 04 c0   .......À
0010: 00 01 00 00 9c 00 00 c0   ....?..À
0018: 00 00 00 00 00 00 00 00   ........
0020: 00 00 00 00 00 00 00 00   ........
0028: 9c cd 34 00 00 00 00 00   ?Í4.....
0030: ff ff ff ff 00 00 00 00   ÿÿÿÿ....
0038: 40 00 00 c4 02 00 00 00   @..Ä....
0040: fe 20 06 12 80 00 00 00   þ ..?...
0048: 00 80 00 00 84 03 00 00   .?..?...
0050: 00 00 68 02 00 8c 7f 88   ..h..??
0058: 00 00 00 00 08 60 4e 86   .....`N?
0060: 00 00 00 00 00 00 00 00   ........
0068: 0a 01 00 00 20 00 00 00   .... ...
0070: 00 00 00 00 60 6d 8e f7   ....`m?÷
0078: 70 00 03 00 00 00 00 1e   p.......
0080: 00 00 00 00 0c 00 00 00   ........
0088: 00 95 00 00 00 00 00 00   .?......

ksdst1's picture

Been in touch with quantum to determine if it is a problem with the drive.  Still on going.

pkh's picture

There is no point in getting in touch with Quantum.  Your tape drive is probably o.k.  The problem is that BE 10d does not support the drive, meaning that your set-up will not work.  You would need to upgrade your BE before you can use your tape drive.

ksdst1's picture

I am in the process of swapping the drive with a warranty replacement.  Everytime i ran the xtalk (quantum) management test i got i/o errors.  They sent me the same make/model so I will swap the drives.  I have no idea if BE will recognise the drive as the old one or add it as another one to the "stand-alone drives".  If it does the later, I hope i dont have to creat all new Jobs and such referencing a "new" drive. 

Ken Putnam's picture

If you delete the old drive before shutting down to add the new one, the new one should get the same name in BackupExec.

If not, then you only need to change your jobs if they are targeted at the device itself, if they are targeted to a loader/library or to "all pools" then you will need to edit the jobs

If this response answers your concern, please mark it as a "solution"

SOLUTION
ksdst1's picture

Tnx for the reply ken....I will try deleting the drive before shutdown.  However, does this mess with the ability to restore from existing tapes that used the original drive to do the backups (perhaps nullifies the cataloging)?

cheers

Ken Putnam's picture

However, does this mess with the ability to restore from existing tapes that used the original drive to do the backups (perhaps nullifies the cataloging)?

Nope.  Backup Exec could care less what drive a tape is created on, as long as the tape volume exists in it's dabatase and the catalog is in the \Catalogs directory

Back aways, I had several dedicated backup servers with anywhere from two to four DLT drives attached to each, and never had any problems

If this response answers your concern, please mark it as a "solution"

ksdst1's picture

tnx for the info ken...i'll give it a try.

best

ksdst1's picture

So I de-enabled my quantum drive, and then deleted it from under the "stand alone drives" list under the server.  I shutdown and swapped the drives, rebooted and the system sees the drive and new serial number but when I open BE 10d the drive does not appear as a detectable drive.  I assumed this would be automatic but as i have not done this before maybe there is a setup. 

I thought i'd post incase there is a very easy answer to this, and while I am looking through the symatec support "how to" entries to see what the procedure might be to add a new stand alone drive.

....Actually, i ran the quantum xTalk test program which includes another round of stopping the BE10d services and then restarting.  The drive is now listed with same name under stand alone drives.  great stuff...

cheers..