locked
Restoring .bak file Error RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    When i adding the back up files(.bak)  into my database by using "Restore Database Option " i got the following error

    I didn't understand why this error happens.Please provide me the solution if anyone knows.

    Thanks,

    Koritala

    Tuesday, March 5, 2013 3:49 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Koritala,

    This means that the backup file is corrupted and will not be able to be used. If this is your only backup, I would suggest taking another and using the new one. If this is an older backup that is part of a restore scenario, you'll need to take a different fork in the recovery path by using other methods. If this is not possible then you're out of luck.

    -Sean

    Sean Gallardy | Blog | Twitter

    • Proposed as answer by Fanny Liu Wednesday, March 6, 2013 10:04 AM
    • Marked as answer by Fanny Liu Monday, March 11, 2013 6:13 AM
    Tuesday, March 5, 2013 7:57 PM
    Answerer

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    There may be corruption in your database. Run a dbcc checkdb on the original database to see if there is any corruption.

    Verify your backup file is fine.

    http://www.mssqltips.com/sqlservertutorial/113/checking-to-make-sure-a-sql-server-backup-is-useable/

    Hope this helps.

    A SQL Server MVP or MSFT Eng should be replying soon as well. Hope this helps. Frank Garcia *** Please select "Vote As Helpful" if the information provided was helpful to you. If an answer to your issue solved the problem then please mark it as "Propose As Answer" located at the bottom. Thank you. ***

    Tuesday, March 5, 2013 4:10 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi Koritala, one option here is to verify that your backup file is not corrupt by running:

    RESTORE VERIFYONLY FROM DISK='e:\your_db.bak'
    There are additional troubleshooting suggestions in the following thread:

    http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/thread/d779d68b-1619-47ca-917a-d89f683dd428/

    Thanks,
    Sam Lester (MSFT)

    My Blog

    This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click "Mark as Answer" and "Vote as Helpful" on posts that help you. This can be beneficial to other community members reading the thread.

    Tuesday, March 5, 2013 4:10 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    There is a consistency issue with your backup file. What happens when you run the following?

    RESTORE VERIFYONLY FROM DISK='Your\Path\And\FileName.Here' WITH CHECKSUM, STATS=5

    -Sean

    Sean Gallardy | Blog | Twitter

    Tuesday, March 5, 2013 4:11 PM
    Answerer
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hai Samuel i runRESTORE VERIFYONLY FROM DISK = 'MY .BAK FILEPATH'
    GO

    I got error Msg 3203, Level 16, State 1, Line 1
    Read on "E:\MY bakfile path.bak" failed: 23(Data error (cyclic redundancy check).)
    Msg 3013, Level 16, State 1, Line 1
    VERIFY DATABASE is terminating abnormally

    when i backup my required database from other system and restore it in my system using restore database option iam getting the same error like in the image i posted above [Cyclic redundancy].

    Thanks,

    Koritala.

    Tuesday, March 5, 2013 6:09 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Sean,

            Im getting the following error

    Msg 3187, Level 16, State 1, Line 1
    RESTORE WITH CHECKSUM cannot be specified because the backup set does not contain checksum information.
    Msg 3013, Level 16, State 1, Line 1
    VERIFY DATABASE is terminating abnormally.

    Thanks,

    Koritala

    Tuesday, March 5, 2013 6:10 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Koritala,

    This means that the backup file is corrupted and will not be able to be used. If this is your only backup, I would suggest taking another and using the new one. If this is an older backup that is part of a restore scenario, you'll need to take a different fork in the recovery path by using other methods. If this is not possible then you're out of luck.

    -Sean

    Sean Gallardy | Blog | Twitter

    • Proposed as answer by Fanny Liu Wednesday, March 6, 2013 10:04 AM
    • Marked as answer by Fanny Liu Monday, March 11, 2013 6:13 AM
    Tuesday, March 5, 2013 7:57 PM
    Answerer
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi there,

    i am sure your backup is corrupted. check the below link exactly similar to your issue.

    http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/thread/48e7d6c6-a872-4681-908e-ab8db3e7ac3c/

    on your database run consistency check and make sure database is ok.

    then take a new backup and try.

    good luck

    kumar

    Tuesday, March 5, 2013 10:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    If it is just to play with backups and if you can restore corrupted database on test environment first then try to run restore database with continue_after_error and then you can execute dbcc checkdb to detect and resolve corruption
    Wednesday, March 6, 2013 4:22 AM