Restoring corrupted backup

  • I have a corrupted backup which I need to restore. I do it using:

    RESTORE DATABASE Test FROM DISK='C:\DB\Test.bak' WITH REPLACE, CONTINUE_AFTER_ERROR

    And getting the error:

    Msg 3013, Level 16, State 1, Line 1

    RESTORE DATABASE is terminating abnormally.

    Msg 3624, Level 20, State 1, Line 1

    A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.

    Looking at the error log I see a line above:

    Error: 17066, Severity: 16, State: 1.

    SQL Server Assertion: File: <bckioreq.cpp>, line=1375 Failed Assertion = '0'. This error may be timing-related.

    If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity,

    or restart the server to ensure in-memory data structures are not corrupted.

  • If continue after error doesn't help, then the backup is completely unrestorable. You'll have to ask for a fresh backup of the DB.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Try dropping the existing database and restore without using the REPLACE option.


    My blog: SQL Soldier[/url]
    SQL Server Best Practices:
    SQL Server Best Practices
    Twitter: @SQLSoldier
    My book: Pro SQL Server 2008 Mirroring[/url]
    Microsoft Certified Master: SQL Server, Data Platform MVP
    Database Engineer at BlueMountain Capital Management[/url]

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply