Operating system error 23 in SQL

  • I scheduled daily backup on tape and it was working fine for two weeks.Last night the backup failed and threw the error BackupTapeFile::SkipFileMark: SetTapePosition failure on backup device '\\.\Tape0'. Operating system error 23(Data error (cyclic redundancy check).).

    Please give me a solution

  • It means the tape or hardware has gone bad.

    This is the probable sequence:

    1. a BAK file is generated and a CRC code is generated

    2. the BAK file is written to tape

    3. the tape is re-read and a CRC code is generate

    The CRC codes from step 1 and 3 don't match. Boom! Time to replace the tape or the tape drive or the computer attached to the tape drive.

  • But today I took the backup of our one database successfully in the tape.But it failed for the second database.I also tried changing the tapes.Our server is DELL Poweredge.

  • Do a checkdb of the db to check if it has any tornpages. Tornpages might cause CRC issues with backups.

    Cheers,
    Sugeshkumar Rajendran
    SQL Server MVP
    http://sugeshkr.blogspot.com

  • Hi there..

    My problem is similar to the one mentioned above, but not the same .. ->

    BackupTapeFile::SkipFileMark: SetTapePosition failure on backup device '\\.\Tape0'. Operating system error 21(error not found).

    This backup job was runing fine too for a long time, and for 3-4 day its making me crazy.

    The scheduled evening backup is faling, but if i run a "manual" backup it's working fine..

    Any ideas?

  • http://answerforu.com/2013/05/05/could-not-open-a-connection-to-sql-server-sql-server-error-code-40/[/url]

  • Please note: 6 year old thread

    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

Viewing 7 posts - 1 through 6 (of 6 total)

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