April 26, 2018 at 4:50 am
hi
i have log shipping enabled on 1 sql instance, been working mostly fine, but all of a sudden backup logs stop applying to the secondary database,possibly after a full db backup has occurred as it thinks there is an earlier backup to apply (there isn't)
018-04-26 08:04:01.23 *** Error: The log in this backup set begins at LSN 978242000018143400001, which is too recent to apply to the database. An earlier log backup that includes LSN 978242000017857200001 can be restored.
RESTORE LOG is terminating abnormally.(.Net SqlClient Data Provider) ***
what i have been told, is the VM that the servers are installed on have moved host, coincidentally as this issue has occurred - could they be connected?
i tried doing a full restore to secondary and started the log shipping again, but the issue has continued!
any ideas?
mal
April 26, 2018 at 6:34 am
You are missing some log backups !
Maybe someone created a log backup out of the normal sequence / location and your log-ship misses that file.
full backups do not break log backup sequences.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
April 26, 2018 at 7:23 am
no thats the thing, i am not missing any backups, no other backups are running
and strangely it will allow me to restore the last log file restored before the .tuf file was created!?
April 26, 2018 at 7:54 am
dopydb - Thursday, April 26, 2018 7:23 AMno thats the thing, i am not missing any backups, no other backups are runningand strangely it will allow me to restore the last log file restored before the .tuf file was created!?
Did you check the backup history from the msdb backup tables? The backupset table has the LSNs - first, last, checkpoint and backup - which could help you identify which backup file it thinks is missing.
Sue
April 26, 2018 at 8:10 am
never even though sue!
and perfect i have found the culprit! a 3rd party has for some reason decided to run random sql log backups in the middle of the night!!!
cheers for help guys
mal
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply