Restoring point in time and transaction log backup file is causing issues

  • The file ID 1 on device '' is incorrectly formed and can not be read. The transaction log backup is doing  checksum and i ran  verifyonly on the transaction log backup file.  We can restore a full, diff and other transaction log files but not this one. I'm running a DBCC CheckDB just to be sure there isn't an issue with the database.

    Any thoughts on what we can do further?

  • Hi,

    can you show your t-sql, where the error happened?

    Best regards,


  • If that log is damaged, there is no way to skip over it than applying a later differential / full depending what the next available none log backup point is.


    Also are you verifying the backups as part of the process?

  • Apart from the advice above, I'd check all of the disks and any place that the backup file sat for any period of time to make sure that you aren't seeing a sign of hardware failure. Probably overkill, but last thing you want to find out is that the disk/tape/cloud provider/whatever holding your backups has failed.

    The above is all just my opinion on what you should do. 
    As with all advice you find on a random internet forum - you shouldn't blindly follow it.  Always test on a test server to see if there is negative side effects before making changes to live!
    I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.

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

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