June 29, 2011 at 12:47 am
Hi,
One of my database is Logshipping configured.All the Log-Backup,Copy,Restore jobs are working perfectly.Eventhough I am getting the below error every 30 minutes..
"
DATE/TIME:29/06/2011 07:30:01
DESCRIPTION:The log shipping primary database GBEXE11DB07.MarshBarclaysHomeSOSPROD_MSCRM has backup threshold of 60 minutes and has not performed a backup log operation for 805 minutes. Check agent log and logshipping monitor information.
COMMENT:(None)
JOB RUN:(None)
"
Backup Job Schedule :
Occurs every day every 15 minute(s) between 12:00:00 AM and 11:59:00 PM. Schedule will be used starting on 6/28/2011.
Alert If No Backup Occurs within 15 Minutes
Copy Job Schedule :
Occurs every day every 15 minute(s) between 12:00:00 AM and 11:59:00 PM. Schedule will be used starting on 6/28/2011.
Restore Job Schedule
Occurs every day every 15 minute(s) between 12:00:00 AM and 11:59:00 PM. Schedule will be used starting on 6/28/2011.
Delay Restoring backups atleast 5 Minutes
Alert If No restore Occurs within 1 Hour
I am using Monitor Instance as my Secondary server and scheduled Alert Job like below:
Occurs every day every 1 hour(s) between 12:00:00 AM and 11:59:59 PM. Schedule will be used starting on 6/28/2011.
Can anyone please let me know why I am getting the above error and how to solve that issue… [Also please let me know which is the best time frequency to schedule all these 4 jobs]
Thanks in advance,
Vamshi
June 29, 2011 at 2:35 am
SQL Agent is handled Log shipping, there's probably a SQL Server Agent job (or a series of such jobs) setup to log ship this database. mpl or look in the Jobs folder as see if you can find the any job(s) that are associated with this, and disable them or just need to remove the rows from the msdb log shipping tables.
Khan
July 4, 2011 at 4:43 am
Similar thing happened with our servers, I can clearly see that the backups are copied and then restored fine at the DR end with no alerts / issues.
All was well until I removed / disabled the log shipping at the primary site for DR test and set it back again next day once the test was done!
I believe during disabling the row in the msdb.dbo.log_shipping_monitor_secondary is not deleted (which might have come from the initial setup) and thus the alert job looks into this table and sends an alert.
What do you reckon?
July 4, 2011 at 5:02 am
execute the following from the monitor instance and post the results
Substitute the values below with your servername and database name
exec master..sp_help_log_shipping_monitor_primary
@primary_server = 'primary_server',
@primary_database = 'primary_database'
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 4, 2011 at 5:42 am
The output is:
00A0903A-7F80-476A-95E5-5BF18FA67C19, 259979-64, FGW, 180, 14420, 1, D:\Shipping\FGW_20110704110000.trn, 2011-07-04 12:00:01.433, 2011-07-04 11:00:01.437, 5760
Just a quick note:
As I had received lots of error emails, I had deleted the row from the msdb.dbo.log_shipping_secondary_mirror table.
Thanks,
Pavan.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply