In the transaction log backup job I run, I have it set up to move the file to another location when it finishes the backup. When I get one of these errors the file is not moved. So since my log shipping job pulls the file from this secondary location it will fail, it attempts to apply the transaction log that occurs after the missing file and then that will fail with
Easy fix, I just move the missing file over and kick off my restore job."SQL error 4305: The log in this backup set begins at LSN 151107000002399800001, which is too late to apply to the database. An earlier log backup that includes LSN 151102000000755100001 can be restored"
But this is where i am a bit confused, this is the file that generated the "760: LSN data from server is blank." error when it was taken. I run "restore sqbheaderonly" and I can see that it is in fact missing the LSN information. But this still restores. I am curious as to why this restores with out errors, and if I should really be doing something different, instead of just applying that transaction log.