Whenever I've seen that error it was always because Log Shipping was truly broken and had to be set-up again.

You say that "the database has been backed up" and that "data is still being shipped OK", however I suspect that you merely mean that the Backup Files and Tran Files are being delivered to the Log Shipping destination server. That isn't all there is to Log Shipping.

The destination server must keep track of the precise sequence of all these files -- and if it somehow loses track of the sequence, then we must start all over again.

How can it lose track? Well, are you certain that a Backup file location wasn't changed? If it changes, it confuses the Log Shipping Database Maintenance Plan.

Last June Michael Beadles sent a workable list of steps to restart Log Shipping from scratch: Here are the steps:

1) delete all data from the msdb.dbo.logshipping tables

2) verify that the maintenance plan no longer shows the log shipping tabs.

3) on source: delete any SQL Agent jobs that are involved in the log
shipping log backup jobs.

4) on destination: delete any SQL Agent jobs that are involved in the log
shipping copy / restore jobs.

5) on source: delete the maintenance plans that are involved in the log
shipping log backup jobs.

6) on source (perhaps after hours) take a full backup.

7) on destination: restore with standby.

8) on source: launch the maintenance plan wizard and re-do the log shipping.

Hope this helps,
--Paul


Richard Wadsworth <mssqldba-ezmlmshield-x81158895.[Email address protected] wrote:
Hi Everyone

I've set up log shipping on a couple of boxes, but I'm getting a bit of
a random error message and I'm wondering if anyone can point me in the
right direction?

The Log Shipping Alert Jon - Backup on the originator is recording an
error every minute

"The log shipping source has not backed up for 1278 minutes.
[SQLSTATE 42000] (Error 14420)."

Even though the database has been backed up. Data is still being
shipped ok - what's the cause of this error??

Any help greatly appreciated/,

Thanks
Rick

MS Sql Server LazyDBA home page