We have a wrong database configured for alert, JKUINMHYU1.JOLRsty should only be a primary database
JKUINMHYU2.JOLRsty should be secondary.
In the mgmt studio, properties of JKUINMHYU1.JOLRsty, transaction log shipping page, We only see JKUINMHYU2.JOLRsty as secondary.
But when we run the following commands, we see a difference.
any way we can remove the the secondary logshipping for JKUINMHYU1.JOLRsty
as run on the primary server JKUINMHYU1
sp_help_log_shipping_monitor
status is_primary server
database_name
time_since_last_backup last_backup_file
backup_threshold is_backup_alert_enabled time_since_last_copy last_copied_file
time_since_last_restore last_restored_file
last_restored_latency restore_threshold is_restore_alert_enabled
------ ---------- -------------------------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------------------------
---------------------- ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
---------------- ----------------------- -------------------- ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
----------------------- ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
--------------------- ----------------- ------------------------
0 1 JKUINMHYU1
JOLRsty
5 e:\JKUINMHYU1\tlogs\JOLRsty_20131202021521.trn
60 1 NULL
NULL
NULL NULL
NULL NULL NULL
NULL 0 JKUINMHYU2
JOLRsty
NULL NULL
NULL NULL NULL
NULL
NULL NULL
NULL NULL NULL
1 0 JKUINMHYU1
JOLRsty
NULL NULL
NULL NULL NULL
NULL
142471 NULL
NULL 45 1
exec sys.sp_check_log_shipping_monitor_alert
Msg 14421, Level 16, State 1, Procedure sp_check_log_shipping_monitor_alert, Line 61
The log shipping secondary database JKUINMHYU1.JOLRsty has restore threshold of 45 minutes and is out of sync. No restore was performed for 142472 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information.
T