January 20, 2009 at 10:46 pm
There is one issue with logshipping as follows in sql servre 2005.
The log shipping secondary database Teddy.BearProduction has restore threshold of 30 minutes and is out of sync. No restore was performed for 115 minutes. Restored latency is 30 minutes. Check agent log and logshipping monitor information. [SQLSTATE 42000] (Error 14421). The step failed.
How to see the logshipping monitor in sql server 2005?
On the secondary I found following information:
Login failed for user 'PHX\CEASTSSA01$'. [CLIENT: 110.97.29.124]
-M
-MJ
Please do not print mails and docx unless it is absolutely necessary. Spread environmental awareness.
January 21, 2009 at 3:30 am
Hi
Check user rights, this might have been changed, if user rights are fine then restore the last restored file, sometimes this weird way works out for me on 2005, but in your case it seems that there is a problem with the user, i would start from there first 🙂
January 21, 2009 at 6:05 am
refer the following link for monitoring:
http://msdn.microsoft.com/en-us/library/ms190224.aspx
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
June 26, 2013 at 7:45 am
hie,
ways to monitor logshipping
run these in msdb database
select * from log_shipping_monitor_alert
select * from log_shipping_monitor_error_detail
select * from log_shipping_history_detail
select * from log_shipping_primary_databases
select * from log_shipping_monitor_primary
select * from log_shipping_secondary_database
select * from log_shipping_primary_secondaries
-->use job history
-->exec sp_help_log_shipping_monitor_primary
exec sp_help_log_shipping_monitor
exec sp_help_log_shipping_monitor_primary
exec sp_help_log_shipping_primary_database
-->use error log
select * from sys.sysmessages where description like '%shipping%' and msglangid=1033
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply