Transaction log shipping together with backup job = conflict?

There is already a backup job plan that runs every 15 minutes. I created transaction log shipping process but afte开发者_JS百科r 1 or two restored logs this job stops working (error: it can't find matching log). Obviously, there are logs created by two individual jobs and for the log shipping process only part of logs are being copied to secondary database (log created by backup job plan are excluded). Does this mean that I will have to turn off backup job plan?

---

The log shipping process does its work by taking log backups. There cannot be another job that does the same, it will break the log backup chain. See Using Log Shipping as Part of a Recovery Plan. Your recovery strategy should clearly document the location of the log backups as taken by the log shipping job and detail step-by-step instructions how to recover the database using these log backups. You should also test this strategy to validate it.

BTW, right now your backup chain is busted as it misses log. You need to take a full database backup to re-seed the chain properly.

---

The comment above is correct, but I'm not sure I'd call the chain "busted" - The two transaction log sets would BOTH be needed to perform a restore - But between both sets of files they ARE available - So you don't need a full database backup to seed the chain - You just need the missing files.

That said this is a highly undesirable situation and confusing to find all the necessary files - but the files ARE available.

Do take a backup, but also do know how to find the files if necessary because you haven't yet taken a backup and need to perform a restore.