Manie Verster (8/15/2012)

---

I have log shipping set up on my database running on SQL Server 2012. It is scheduled to run Monday to Friday, 07:00 am to 17:00 pm. It runs perfectly in the alotted time but throws errors every two minutes for the time it does not need to run. Error below:

The log shipping primary database SQL\ORISYS.OrisysSQL has backup threshold of 60 minutes and has not performed a backup log operation for 170 minutes. Check agent log and logshipping monitor information. I never got this before it just suddenly started since the weekend.

Please can someone help me out here?

Manie Verster (8/15/2012)

---

Yes! I know but how and to what? I don't have a cooking clue. Can you help maybe, Perry?

exec sp_change_log_shipping_primary_database @database = 'yourdb'
, @backup_threshold = 'backup_threshold in mins' 

exec sp_change_log_shipping_primary_database @database = 'yourdb'
, @threshold_alert_enabled = '1' 

exec sp_change_log_shipping_secondary_database
@secondary_database = 'yourdb'
, @restore_threshold = 'restore_threshold in mins' 

exec sp_change_log_shipping_secondary_database
@secondary_database = 'yourdb'
, @threshold_alert_enabled = '1'

Perry Whittle (8/15/2012)

---

as Anthony said above really.

You could also use the stored procedures to do this via T-SQL instead of the GUI. On the primary use this to set the threshold

exec sp_change_log_shipping_primary_database @database = 'yourdb'
, @backup_threshold = 'backup_threshold in mins' 

or disable the backup threshold alert using

exec sp_change_log_shipping_primary_database @database = 'yourdb'
, @threshold_alert_enabled = '1' 

On the secondary up the threshold using

exec sp_change_log_shipping_secondary_database
@secondary_database = 'yourdb'
, @restore_threshold = 'restore_threshold in mins' 

or disable using

exec sp_change_log_shipping_secondary_database
@secondary_database = 'yourdb'
, @threshold_alert_enabled = '1'