January 23, 2010 at 12:12 pm
Just had a doubt on log shipping job failures I am facing.
On primary server, the log shipping transaction log is running successfully.
But on secondary server, the copy job is failing but the restore is successful.
And the log shipping monitor, is showing that the primary and secondary are in sync.
This shouldn't be the case right?
When copy job is failing how could restore happen.
M&M
January 23, 2010 at 3:55 pm
If the copy job is truly failing, then it shouldn't be able to restore and be in synch.
Are you copying to multiple locations by chance?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
January 23, 2010 at 4:07 pm
the restore job will still show as successful when it has no logs to restore, if the copy is not happening there will be none to restore, so the restore job is happy. So check the errorlog to see when the last restore actually happened, and check the tables in msdb as well (they have such long names I can never remember them).
the dbs will not show as out of synch until whatever threshold you have set is exceeded.
Why is the copy failing? Its usually permissions or a typo in defining its location.
---------------------------------------------------------------------
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply