Skipped Log Backup File ..... Could not find a log backup file that could be applied to secondary Database
What does this mean?
I've configured a log shipping. To test, I created 2 tables, put values on them, created another 2 and etc.
During the first run of the job, is says the message above.
Later, let's say after 2 or 3 runs, the log shipping starts to modify the secondary database.
Why this happens during the firsts runs?
Even if I use
checkpoint I see that error.
In this post Here Says something:
The Restore job finds no suitable log files to apply in location B because they are all being backed up to location A and NOT being copied over to B (due to the Copy job being disabled).
I'm with 2 windows oppened and I can see both jobs working ( I can see the backup log job ( because I can see files being created )), and I can see the copy is working too ( files are being created on the second window too).
And, a bonus question...I want to log shipping from
SQL 2012 to
SQL 2014. So, I need to use "no recovery" option right? because I can't use
stand by with a higher version on the secondary. Or am I wrong?