I apologize in advance for a long post, but I have had it up to here with the situation of having to delete Log Shipping (LS) configuration and starting it over for any DB that has got this error.
I have LS setup on 3 win2k8r2 servers (primary, secondary, monitor) with 100 databases backed up and shipped transactions from the primary to secondary and monitored by monitor. Backups and copies are run every 15 mins and then the ones older than 24 hrs are deleted.
Some DBs are very active and some not so active but shipped regardless for uniformity sake (basically to make secondary server identical to primary). Some DBs are for SharePoint 2010 and the majority are for inhouse apps.
The issue is that after all LS configs are set up, everything works well for about 3 to 4 days. Then I go to the Transaction LS Status report on the secondary, I see that randomly some LS jobs have an Alert Status, because the time since last copy is over 45 mins so no restore has occurred. This seems random and the only errors I see is from a SharePoint 2010 DB (WebAnalyticsServiceApplication_ReportingDB_77a60938_##########) which I belive is a Reporting DB that gets created weekly and LS just cannot figure out which the last copy to backup or to restore is.
I posted here regarding that and I have yet to find a permanent solution.
For my main error (time since last copy) I have not seen anything that could have caused that and I don't get any messages (even though some alert statuses have been ignored for 3 days).
Anyway, I would really appreciate any input on understanding what's causing this issue and how I could fix it.