backup with checksum failes, dbcc checkdb is ok

  • Hi,

    I am using SQL Server 2005 standard SP3, doing a backup as follows:

    BACKUP DATABASE db1

    TO DISK = '\\whatever\DatabaseBackups\db1.BAK'

    WITH INIT,

    NAME ='Backup data of db1',

    CHECKSUM

    I am getting the following error:

    BACKUP 'db1' detected an error on page (1:107675) in file 'D:\db1.MDF'.

    dbcc checkdb is ok:

    CHECKDB found 0 allocation errors and 0 consistency errors in database 'MyDb'.

    DBCC execution completed. If DBCC printed error messages, contact your system administrator.

    Did anyone encountered such a scenario and if so, what is the solution?

  • Try the backup again?

    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
  • When i backup without the checksum option, the backup runs ok...

  • Yes it will, that's not what I asked.

    Try the backup again, exactly as you did before.

    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
  • Same error...

    Even if i change the backup to a local drive.

  • Checksum failed for db1.mdf and you run checkdb for Mydb. I guess they both are same.

  • enriquemallon (9/10/2014)


    Checksum failed for db1.mdf and you run checkdb for Mydb. I guess they both are same.

    Are these the same? Or two different databases?

  • This was removed by the editor as SPAM

  • get info here: SQL Server Fix Toolbox

    Use this site: http://www.fixsqldatabase.com/[/url]

  • The issue was solved by opening a ticket at MS support.

    After a week or so they replied that it was identified as a bug within SQL Server and that it would be fixed in future versions.

Viewing 10 posts - 1 through 9 (of 9 total)

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