October 10, 2024 at 3:54 pm
I'm using Ola's backup script to back up my databases. One database has recently started throwing an error during the verify portion of the restore - complaining that the backup does not contain a checksum - even though I told SQL to include one. Here is the output from Ola's script:
Command: BACKUP LOG [Business] TO DISK = N'\\xxxxxx\sql_backups$\Business\LOG\Business_20241010084500.trn' WITH CHECKSUM, COMPRESSION
Processed 3 pages for database 'Business', file 'Business_log' on file 2.
BACKUP LOG successfully processed 3 pages in 0.034 seconds (0.689 MB/sec).
Outcome: Succeeded
Duration: 00:00:00
Date and time: 2024-10-10 08:45:00
Date and time: 2024-10-10 08:45:00
Database context: [master]
Command: RESTORE VERIFYONLY FROM DISK = N'\\xxxxxx\sql_backups$\Business\LOG\Business_20241010084500.trn' WITH CHECKSUM
Msg 3187, Sev 16, State 1, Line 1 : RESTORE WITH CHECKSUM cannot be specified because the backup set does not contain checksum information.
I'm clearly specifying WITH CHECKSUM. Furthermore, this doesn't happen with every backup. Sometimes it does not error out.
Anyone seen something like this before?
October 10, 2024 at 6:42 pm
Figured this out.. I was setting up log shipping to seed a new AG replica. As part of that, I removed the log backups from Ola's script and used the job from the log shipping wizard. Then I stopped log shipping and went back to Ola's job only. Apparently, the two processes use different timezones for creating their timestamp-based names, but sometimes the timing was such that the names generated were the same. So I was ending up with log backup files with 2 backup sets in them - one from Ola's job, which had a checksum, and one from the log shipping job without the checksum.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply