Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Log shipping throw errors Expand / Collapse
Author
Message
Posted Wednesday, August 15, 2012 12:40 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Friday, July 25, 2014 5:21 AM
Points: 1,205, Visits: 923
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
Developer
Johannesburg
South Africa

I can do all things through Christ who strengthens me. - Holy Bible
I am a man of fixed and unbending principles, the first of which is to be flexible at all times. - Everett Mckinley Dirkson (Well, I am trying. - Manie Verster)
Post #1345139
Posted Wednesday, August 15, 2012 2:10 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 12:54 PM
Points: 6,282, Visits: 13,538
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?

You'll need to change your threshold allowances to suit your backup and restore timeframes.


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1345155
Posted Wednesday, August 15, 2012 2:51 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Friday, July 25, 2014 5:21 AM
Points: 1,205, Visits: 923
Yes! I know but how and to what? I don't have a cooking clue. Can you help maybe, Perry?

Manie Verster
Developer
Johannesburg
South Africa

I can do all things through Christ who strengthens me. - Holy Bible
I am a man of fixed and unbending principles, the first of which is to be flexible at all times. - Everett Mckinley Dirkson (Well, I am trying. - Manie Verster)
Post #1345174
Posted Wednesday, August 15, 2012 3:05 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 6:20 AM
Points: 5,218, Visits: 5,067
Are you bothered about the alerts during the weekend as well as the weekdays?

If so you will need to set the alert to 62 hours for a backup threshold if not then 14 hours.

To do the change, open up the log shipping configuration from the primary server and database and press the backup settings button, on that screen you should see "Alert if no backup occurs within" and you can then specify the threshold.

Edit.

You will then have to look at the restore thresholds as they will then start to error if it cannot restore due to no backups being taken.

Same as above, but then select the secondary and click the elipsis button next to the secondary database, and on the restore transaction log tab, change the "Alert in no restore occures within" threshold to match.




Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1345177
Posted Wednesday, August 15, 2012 3:58 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 12:54 PM
Points: 6,282, Visits: 13,538
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?

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'



-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1345191
Posted Monday, August 20, 2012 1:41 PM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Yesterday @ 8:40 AM
Points: 2,692, Visits: 3,383
Perry Whittle (8/15/2012)
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?

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'

Shouldn't those 1's be 0's if you are disabling


Thanks,

Jared
SQL Know-It-All

How to post data/code on a forum to get the best help - Jeff Moden
Post #1347447
Posted Monday, August 20, 2012 10:25 PM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, March 21, 2014 9:46 AM
Points: 387, Visits: 1,078
If I understood correctly, we are going to avoid false alert from 5pm to 7am by raising threshold value. Then, we will not be notified of actual lag in normal hours( 7am to 5pm)?.
Post #1347559
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse