September 18, 2023 at 7:25 pm
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?
September 19, 2023 at 5:17 am
Hi,
can you show your t-sql, where the error happened?
Best regards,
Andreas
September 19, 2023 at 7:48 am
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?
September 19, 2023 at 10:07 pm
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.
September 30, 2023 at 5:31 am
Please run a "checkdsk /f" operation to see if there are hardware drive issues as stated above. Then try the restore process.
Other than that, I would copy the backup files to another SQL server to see if you can reuse the failing log backup to restore the database.
If this fails, the log backup may not be usable.
DBASupport
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply