June 15, 2011 at 7:12 am
Hi all,
What would be the best way to check my Log Shipping database on accuracy? Reason for asking is that I’ve had positive feedback in the past that the Log Shipping database was up to date but in fact it was a week behind (I was checking msdb for last restored, but it gave a false positive). 😉
Running SQL2008 R2 on Windows 2008 R2
Grt Dimitry
June 15, 2011 at 7:20 am
last log restored information should be good enough, but you could add your own table to the primary, update on a regular interval and check the value in the secondary.
---------------------------------------------------------------------
June 15, 2011 at 7:27 am
george sibbald (6/15/2011)
last log restored information should be good enough, but you could add your own table to the primary, update on a regular interval and check the value in the secondary.
George,
Thanks for the replay. About two seconds before your reply I thought of exactly the same.. Nice to know I was on the right track...:-P
June 15, 2011 at 7:30 am
there is a logshipping alert which will warn you if the secondary is out of synch by more than a set amount.
2 secs before or 2 secs after? 🙂
---------------------------------------------------------------------
June 15, 2011 at 7:43 am
George,
The alert is up and running. I only recently upgraded from SQL 2000 to SQL 2008 R2. Now the problem is that log shipping SQL 2000 is not all that stable and a log shipping database was behind about a week, but this was noticed by an employee. Thus my boss wants this extra check for the time being.
Thanks again..
Grt Dimitry
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply