February 16, 2022 at 5:51 pm
I have a weird situation regarding log shipping. We back up the databases on our production database server every hour, and then restore to our reporting server. This has been running for years.
Last weekend, we upgraded our accounting system, and afterwards, log shipping stopped on the databases that the accounting system users. There is no error - the log restore simply skips any log backups and finishes with a message saying "Could not find a log backup file that could be applied to secondary database."
I tried dropping and recreating the log shipping a couple of times, and finally got it to work again - but it bothers me that I don't know exactly *why* it failed in the first place, or frankly even why it finally succeeded. I basically just used the wizard for log shipping.
Any ideas would be appreciated... it's working now, but I want to understand in case this happens again.
February 17, 2022 at 6:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
February 18, 2022 at 2:35 pm
Some additional information: I found a fairly consistent "fix" which was renaming the backup set for each database.
Still not clear on *why* that works, though.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply