none
Tape Backup Fails After Partial Backup * ID 30101 Details: Data error (cyclic redundancy check) (0x80070017) RRS feed

  • Question

  • I have a fairly new LTO4 tape that has been acting up lately.  I get the error: Library Drive Not functioning

    When I look at the tape the Clean & the Tape LED are flashing yellow, if I power tape off and back on the Clean light comes on,  so I do a clean (clean tape is April 2013 used once weekly) and then the Ready LED is solid Green.  I had this issue with my old LTO3 tape, but do not remeber how I fixed it.

    I tried running SFC /scannow as domain Admin and Administrator getting you need to have administrative rights to run this.

    I found a post telling the user to add StorPort dWord and busyRetryCount with value as 250, however this was for HP StorageWorks Ultrium Tape Drive is connected to a LSI based Host Bus Adapter.  So I was not sure if I should do this or not??

     This is my error:

    Affected area:   Quantum LTO 4 Tape Drive

    Occurred since: 9/13/2013 9:02:58 PM

    Description:        Library drive Quantum LTO 4 Tape Drive in Quantum LTO 4 Tape Drive is not functioning and library jobs may fail until the drive is repaired.  The drive is not functioning for the following reason:

     (ID 3303)

                    DPM encountered a critical error while performing an I/O operation on the tape FS & AP servers-00000003 (Barcode - ) in Drive Quantum LTO 4 Tape Drive. (ID 30101 Details: Data error (cyclic redundancy check) (0x80070017))

    Recommended action:  Retry the operation. If the problem persists, contact your hardware vendor.

                    No action required

    Resolution:         To dismiss the alert, click below

                    Inactivate alert

    I will retry tape backup or maybe even another tape as this one may be locked now.


    Peter Jam


    Sorry, remebered I needed to be at console to run SFC and not RDP.  That is running now.
    • Edited by pjamme Monday, September 16, 2013 7:32 PM SFC comment
    Monday, September 16, 2013 1:35 PM

All replies

  • HI,

    You pretty much have to take CRC error 0x80070017 at face value.  Check cabling and termination, cooling, tape storage conditions and keep records of tapes that report the error.  It just takes one bad tape to contaminate other tapes.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Monday, September 16, 2013 9:31 PM
    Moderator
  • Mike,

    I think it must be a timing issue.  All my backups ran this Saturday except System State PG.  I do not think it is running out of space yet, but that might be the issue.  Last week I had to use 3 tapes to get what I did on the first LTO4 Saturday.  I out in a 2nd LTO3 tape as that is all I had and Ssytem State backup just fine.   DPM Event says:

    Event Type: Error
    Event Source: DPM-EM
    Event Category: None
    Event ID: 1
    Date:  9/21/2013
    Time:  3:56:07 AM
    User:  N/A
    Computer: SLOSSIF01
    Description:

    The back up to tape job failed for the following reason: (ID: 3311)
    Failed to perform the operation since the tape free tape is not available in Stand Alone Drive Tape Library Quantum LTO 4 Tape Drive (ID: 24050)


    DPM ID: 4^|^SLOSSIF01^|^Backup to tape failed^|^DPM^|^Tape^|^SLOSSAP01.smiths.net^|^d73ea09d-17dd-45c2-bdf3-a20c4653211e

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


    Peter Jam

    Monday, September 23, 2013 3:24 PM
  • Hi,

    OK - You can adjust the prompting timeout to give you more time to change the tape so the backup does not fail due to not having free tape.

    See: http://social.technet.microsoft.com/Forums/en-US/919109c4-39b9-4922-a811-b7b6a3e07440/dpm-2010-stoped-taking-backup


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Monday, September 23, 2013 5:08 PM
    Moderator
  • Thanks Mike, we will see what happens this Saturday.

    Peter Jam

    Monday, September 23, 2013 5:37 PM
  • Mike,

    Still did not work, and I have a question about backups.  I have four Protection Groups:

    1. DPMB (not encrypted and run on 3rd Wed of month)
    2. System State (not encrypted and run on Saturday)
    3. SQL backups (Encrypted and run on Saturday)
    4. ERP & FS (encrypted and run on saturday)

    This Saturday the System State backed up to LTO4 tape, but not number 3 & 4

    SQL replica was inconsistent again so can understand why it did not backup.  In fact I am still getting the error below when it tells me to clear the VSS and Run Syschronization continues to fail.

    My question is this, is the fact that one of my 3 Saturday jobs not encrypted causing this to happen.  If not, where do I start?

    Also why do I continually have an issue with the SQL Backups and VSS?  Is there an issue on the SQL server itself?

    On another note, this web site has an annoying script that continually stops IE8, why is that?

    -------An unexpected error occurred during a VSS operation.

    Retry the operation.

    ID: 207

    Details: Unknown error (0x80042306) (0x80042306)


    Peter Jam

    Tuesday, October 1, 2013 1:01 PM
  • Hi,

    Please update the stored procedure from this blog - it can help resolve LT tape backups that do not run at scheduled times:

    http://blogs.technet.com/b/dpm/archive/2012/09/24/support-tip-scheduled-backup-to-tape-runs-on-a-wrong-date-on-dpm-2007-2010-and-2012.aspx

    The VSS errors will need to addressed on the SQL Server - may want to ensure you have latest SQL Server writer and VSS fixes installed. 


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Tuesday, October 1, 2013 3:10 PM
    Moderator
  • Mike,

    I will see if someone can help with making sure we have most current SQL Server writer and VSS, I am not into DB.  It is SQL 2005 and this is the result of

    Microsoft Windows [Version 5.2.3790]
    (C) Copyright 1985-2003 Microsoft Corp.

    C:\Documents and Settings\Username>vssadmin list writers
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001 Microsoft Corp.

    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {dbd72c04-28fc-436b-9bf3-3a6a5d84ec0b}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'SqlServerWriter'
       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
       Writer Instance Id: {6795427f-dd42-4c67-a227-a116f3eaad8f}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'MSDEWriter'
       Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
       Writer Instance Id: {ef595766-0b97-46fb-a400-c676097526d8}
       State: [1] Stable
       Last error: No error

    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {5da6de93-04c1-4e46-a1ab-69716a007820}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {c2a1ef7a-a6da-4a04-8f76-4b79d7f4da6d}
       State: [1] Stable
       Last error: No error

    Writer name: 'Event Log Writer'
       Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
       Writer Instance Id: {43b20c44-aa37-4f45-ad30-5ed10fb294d1}
       State: [1] Stable
       Last error: No error

    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {525dabbc-62ff-45bd-a7b9-320614179702}
       State: [1] Stable
       Last error: No error

    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {b9fc86cf-4b2d-477b-85fd-8c7b71059418}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'BITS Writer'
       Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
       Writer Instance Id: {1bba1394-1abb-4aee-b907-281827282b57}
       State: [5] Waiting for completion
       Last error: No error


    Peter JamIt also says to run chkdsk on volume \\?\Volume{d90a334b-6f3d-4daa-86b9-8f8bd6159f5d}\, and I get This type of file is RAW.  CHKDSK is not available for RAW drives.


    • Edited by pjamme Tuesday, October 1, 2013 3:59 PM added another comment regardin CHKDSK
    Tuesday, October 1, 2013 3:44 PM
  • Mike,

    i read through that Blog, quite scary.  However it says it is not applicable to DPM 2007:

    NOTE: This issue does not affect daily, weekly, or monthly tape backup schedules, it primarily affects tape backups that are in multiples of months, like quarterly, semi-annually, yearly etc. This issue is presented on DPM 2007, 2010 and 2012 but this workaround is not applicable to DPM 2007.


    Peter Jam

    Tuesday, October 1, 2013 5:34 PM
  • Hi,

    That is correct the problem is present in DPM 2007, but the stored procedure workaround is not valid  for DPM 2007.

    Only options if that is indeed the cause of your issue is:

    A) Live with the possibility that some tape backup jobs may not run as scheduled.
    B) Upgrade to DPM 2010 so the workaround can be applied.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Tuesday, October 1, 2013 6:08 PM
    Moderator
  • Mike,

    I changed schedule of all four PG to be as near identical as possible.  Everything backup tup to tape except the PG for SQL backups and it fails immediately when I try to re-run synchronization.

    If I click on "Clear the VSS vault" I get this error:


    Peter Jam

    I rebooted the server and did not get an error clearing the VSS vault and verification is in progress.

    I will check back tomorrow

    Well it is still inconistant, so either did not finish or this is new.  New I think since time says 12:47 AM today.  And I get the error again trying to clear VSS Fault.

    An unexpected error occurred during a VSS operation.

    Retry the operation.

    ID: 207

    Details: Unknown error (0x80042306) (0x80042306)

    • Edited by pjamme Tuesday, October 8, 2013 11:59 AM updated
    Monday, October 7, 2013 5:43 PM
  • Mike,

    A lot has taken place, sorry to say this has consumed all my time.

    Apparently there were three failing disks in the MSA20 array.  I had two spares and replaced one in each volume, but the third disk damage volume 1 to the point where there was corruption.  Then Recovery Point Volume needed more more space. I guess since it could not use Volume 1 anymore and I gave it too much.  Volume 0 now has 0% unallocated. Volume 1 is saying 44% unallocated and is green after a shutdown. I ordered larger hard drive for Volume 1. 

    How do I proceed?


    Peter Jam


    • Edited by pjamme Thursday, October 24, 2013 2:40 PM updated
    Thursday, October 24, 2013 2:14 PM
  • Mike,

    A lot has taken place, sorry to say this has consumed all my time.

    Apparently there were three failing disks in the MSA20 array.  I had two spares and replaced one in each volume, but the third disk damage volume 1 to the point where there was corruption.  Then Recovery Point Volume needed more more space. I guess since it could not use Volume 1 anymore and I gave it too much.  Volume 0 now has 0% unallocated. Volume 0 only has about 6GB free, apparently all that I allocated went here rather than half to each volume.

    Volume 1 is saying 44% unallocated and is green after a shutdown. I ordered larger hard drive for Volume 1.  Volume 1 does not seem to be working even though DPM says it is healthy with 600GB free.

    If I stop protection will I get that allocated back that is not used?  My plan was to remove the 6 250GB from Disk 1, since it has one bad hard drive and does not seem to accept backups and replace those with 6 750GB that should be here toward the end of the week.

    How do I proceed?


    Peter Jam

    Event Viewer has this error:

    Event Type:    Error
    Event Source:    Ntfs
    Event Category:    Disk
    Event ID:    55
    Date:        10/30/2013
    Time:        8:00:05 PM
    User:        N/A
    Computer:    SLOSSIF01
    Description:
    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume DPM-Non VSS Datasource Writ.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 0c 00 04 00 02 00 52 00   ......R.
    0008: 02 00 00 00 37 00 04 c0   ....7..À
    0010: 00 00 00 00 02 01 00 c0   .......À
    0018: 00 00 00 00 00 00 00 00   ........
    0020: 00 00 00 00 00 00 00 00   ........
    0028: 17 0b 14 00               ....    

    Does not help me determine what need fixing, and I do not believe I am supposed to run chkdsk on MSA 20 disks, am I?

    Ran HP Array diags and it is showing nothing wrong?

    I removed the PG for everything, removed the HP Logical volumes and am starting from scratch.  We will see how backups and tape go this week.

    Replaced one side of the MSA with new 750GB disks

    • Edited by pjamme Tuesday, November 5, 2013 8:38 PM update
    Tuesday, October 29, 2013 12:37 PM