August 10, 2016 at 1:46 pm
Environment and Server Details:
- 12.0.4457
- Windows Server 2012 R2 standard
- VMWare Virtual Machine
- Dell Equal Logic SAN
SQL Error Log Message:
[font="Times New Roman"]The log shipping secondary database ServerName.DatabaseName has restore threshold of 45 minutes and is out of sync. No restore was performed for 34089 minutes. Restored latency is 2 minutes. Check agent log and log shipping monitor information.[/font]
I've verified that the logs are being restored on the log shipping secondary, matched up the LSNs, also, I have the Log Shipping Monitor from Red Gate that verifies my logs are up to date. Further, the aforementioned error message is for every database in the instance.
I've built a similar setup in a lab environment and I get the same error messages.
Having 10s of thousands of error messages per week makes it pretty difficult to peruse and check other possible issues :crazy:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
One of the greatest tragedies in life is to lose your own sense of self and accept the version of you that is expected by everyone else.
August 10, 2016 at 2:31 pm
Are you using the Red Gate log shipping feature or the native Sql Server log shipping utility to perform the log shipping?
August 10, 2016 at 3:39 pm
The Red Gate Shipping Monitor is just a monitoring software to inform me that log shipping is working in all its facets.
I'm using the native Log Shipping in SQL Server.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
One of the greatest tragedies in life is to lose your own sense of self and accept the version of you that is expected by everyone else.
August 10, 2016 at 3:47 pm
When you run this query on the secondary, do the results look accurate?
select lss.primary_server,lsms.secondary_server,lss.primary_database,lsms.secondary_database,
lss.backup_source_directory,lss.backup_destination_directory,
lss.file_retention_period [backup file retention period on disk in mins],lss.last_copied_file,lss.last_copied_date,
lssd.restore_delay [Delay time set for resore (Mins)],lssd.disconnect_users [Dissconnect users while restore],
lsms.restore_threshold [Restore threshold in Mins],
lsms.last_copied_file,lsms.last_copied_date,lsms.last_restored_file,lsms.last_restored_date,DATEDIFF(MINUTE,lsms.last_restored_date,getdate()) [Restoration Not happened from (Mins)]
from
msdb.dbo.log_shipping_secondary lss join
msdb.dbo.log_shipping_secondary_databases lssd
on lss.secondary_id = lssd.secondary_id
join msdb.dbo.log_shipping_monitor_secondary lsms
on lss.secondary_id = lsms.secondary_id
August 24, 2016 at 3:58 pm
yes, the result set from your posted query shows accurate information. It shows the same information the Log Shipping Monitor from Red-Gate shows.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
One of the greatest tragedies in life is to lose your own sense of self and accept the version of you that is expected by everyone else.
August 25, 2016 at 1:47 am
Do both servers have the same time settings?
Alternatively, what are the schedules for the jobs? I've seen this message when log-shipping was scheduled to pause overnight then resume in the morning. In that example it wasn't an error.
August 25, 2016 at 9:25 am
I've verified that the system time on both are exactly in sync within one second or less. Also, there is no pausing of the jobs at an any time, the job history shows they're running every 15 minutes (default config) 24/7 with no failures.
This is a perplexing issue, I've looked at all the seemingly obvious stuff, and there is nothing that points to why SQL Server is reporting sync errors. It is like there is an invisible history table these jobs are talking to and reporting on that is incorrect.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
One of the greatest tragedies in life is to lose your own sense of self and accept the version of you that is expected by everyone else.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply