March 9, 2011 at 2:04 am
Guys ,
I'm in a critical situation .
i join a new organization and discovered that there is no DR /BCP in Place and their is no budget for it until next year.
in order to mitigate my risk as the DBA we set up a virtual engine to house BCP for the DB server
we have sql server 2008R2 installed and setup a log shipping arrangement between the Production server and the the virtual engine which was ssuccessful but when i checked the sql log two day later all I got was the message below . is there any i did wrong or is it not possible to log ship transaction between Sql Server 2008 and Sql Server 2008R2 and the production server is runing Sql Server 2008:
LOG:
03/09/2011 08:20:00,spid65,Unknown,The log shipping secondary database RIND.erplndb has restore threshold of 120 minutes and is out of sync. No restore was performed for 2844 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information.
03/09/2011 08:20:00,spid65,Unknown,Error: 14421<c/> Severity: 16<c/> State: 1.
03/09/2011 08:18:00,spid71,Unknown,The log shipping secondary database RIND.erplndb has restore threshold of 120 minutes and is out of sync. No restore was performed for 2842 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information.
03/09/2011 08:18:00,spid71,Unknown,Error: 14421<c/> Severity: 16<c/> State: 1.
03/09/2011 08:16:00,spid79,Unknown,The log shipping secondary database RIND.erplndb has restore threshold of 120 minutes and is out of sync. No restore was performed for 2840 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information.
03/09/2011 08:16:00,spid79,Unknown,Error: 14421<c/> Severity: 16<c/> State: 1.
03/09/2011 08:14:00,spid76,Unknown,The log shipping secondary database RIND.erplndb has restore threshold of 120 minutes and is out of sync. No restore was performed for 2838 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information.
03/09/2011 08:14:00,spid76,Unknown,Error: 14421<c/> Severity: 16<c/> State: 1.
03/09/2011 08:12:00,spid76,Unknown,The log shipping secondary database RIND.erplndb has restore threshold of 120 minutes and is out of sync. No restore was performed for 2836 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information.
03/09/2011 08:12:00,spid76,Unknown,Error: 14421<c/> Severity: 16<c/> State: 1.
03/09/2011 08:10:00,spid68,Unknown,The log shipping secondary database RIND.erplndb has restore threshold of 120 minutes and is out of sync. No restore was performed for 2834 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information.
03/09/2011 08:10:00,spid68,Unknown,Error: 14421<c/> Severity: 16<c/> State: 1.
03/09/2011 08:08:00,spid64,Unknown,The log shipping secondary database RIND.erplndb has restore threshold of 120 minutes and is out of sync. No restore was performed for 2832 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information.
03/09/2011 08:08:00,spid64,Unknown,Error: 14421<c/> Severity: 16<c/> State: 1.
03/09/2011 08:06:00,spid71,Unknown,The log shipping secondary database RIND.erplndb has restore threshold of 120 minutes and is out of sync. No restore was performed for 2830 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information.
03/09/2011 08:06:00,spid71,Unknown,Error: 14421<c/> Severity: 16<c/> State: 1.
03/09/2011 08:04:00,spid68,Unknown,The log shipping secondary database RIND.erplndb has restore threshold of 120 minutes and is out of sync. No restore was performed for 2828 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information.
03/09/2011 08:04:00,spid68,Unknown,Error: 14421<c/> Severity: 16<c/> State: 1.
03/09/2011 08:02:00,spid68,Unknown,The log shipping secondary database RIND.erplndb has restore threshold of 120 minutes and is out of sync. No restore was performed for 2826 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information.
03/09/2011 08:02:00,spid68,Unknown,Error: 14421<c/> Severity: 16<c/> State: 1.
03/09/2011 08:00:00,spid76,Unknown,The log shipping secondary database RIND.erplndb has restore threshold of 120 minutes and is out of sync. No restore was performed for 2824 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information.
03/09/2011 08:00:00,spid76,Unknown,Error: 14421<c/> Severity: 16<c/> State: 1.
03/09/2011 07:58:00,spid71,Unknown,The log shipping secondary database RIND.erplndb has restore threshold of 120 minutes and is out of sync. No restore was performed for 2822 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information.
03/09/2011 07:58:00,spid71,Unknown,Error: 14421<c/> Severity: 16<c/> State: 1.
03/09/2011 07:56:00,spid78,Unknown,The log shipping secondary database RIND.erplndb has restore threshold of 120 minutes and is out of sync. No restore was performed for 2820 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information.
03/09/2011 07:56:00,spid78,Unknown,Error: 14421<c/> Severity: 16<c/> State: 1.
03/09/2011 07:54:00,spid55,Unknown,The log shipping secondary database RIND.erplndb has restore threshold of 120 minutes and is out of sync. No restore was performed for 2818 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information.
03/09/2011 07:54:00,spid55,Unknown,Error: 14421<c/> Severity: 16<c/> State: 1.
03/09/2011 07:52:00,spid81,Unknown,The log shipping secondary database RIND.erplndb has restore threshold of 120 minutes and is out of sync. No restore was performed for 2816 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information.
03/09/2011 07:52:00,spid81,Unknown,Error: 14421<c/> Severity: 16<c/> State: 1.
03/09/2011 07:50:00,spid73,Unknown,The log shipping secondary database RIND.erplndb has restore threshold of 120 minutes and is out of sync. No restore was performed for 2814 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information.
03/09/2011 07:50:00,spid73,Unknown,Error: 14421<c/> Severity: 16<c/> State: 1.
03/09/2011 07:48:00,spid73,Unknown,The log shipping secondary database RIND.erplndb has restore threshold of 120 minutes and is out of sync. No restore was performed for 2812 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information.
03/09/2011 07:48:00,spid73,Unknown,Error: 14421<c/> Severity: 16<c/> State: 1.
03/09/2011 07:46:00,spid78,Unknown,The log shipping secondary database RIND.erplndb has restore threshold of 120 minutes and is out of sync. No restore was performed for 2810 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information.
03/09/2011 07:46:00,spid78,Unknown,Error: 14421<c/> Severity: 16<c/> State: 1.
03/09/2011 07:44:00,spid65,Unknown,The log shipping secondary database RIND.erplndb has restore threshold of 120 minutes and is out of sync. No restore was performed for 2808 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information.
03/09/2011 07:44:00,spid65,Unknown,Error: 14421<c/> Severity: 16<c/> State: 1.
03/09/2011 07:42:00,spid78,Unknown,The log shipping secondary database RIND.erplndb has restore threshold of 120 minutes and is out of sync. No restore was performed for 2806 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information.
03/09/2011 07:42:00,spid78,Unknown,Error: 14421<c/> Severity: 16<c/> State: 1.
03/09/2011 07:40:00,spid71,Unknown,The log shipping secondary database RIND.erplndb has restore threshold of 120 minutes and is out of sync. No restore was performed for 2804 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information.
03/09/2011 07:40:00,spid71,Unknown,Error: 14421<c/> Severity: 16<c/> State: 1.
03/09/2011 07:38:00,spid67,Unknown,The log shipping secondary database RIND.erplndb has restore threshold of 120 minutes and is out of sync. No restore was performed for 2802 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information.
03/09/2011 07:38:00,spid67,Unknown,Error: 14421<c/> Severity: 16<c/> State: 1.
03/09/2011 07:36:00,spid76,Unknown,The log shipping secondary database RIND.erplndb has restore threshold of 120 minutes and is out of sync. No restore was performed for 2800 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information.
03/09/2011 07:36:00,spid76,Unknown,Error: 14421<c/> Severity: 16<c/> State: 1.
March 9, 2011 at 2:33 am
Log shipping between versions does work, but bear in mind if the prod server ever fails and you have to use the DR box, you'll never be able to go back to SQL 2008 (downgrade of the version is not permitted). I don't recommend disparate versions except during an upgrade process.
The error just says there hasn't been a restore in the threshold time. Check that the jobs to copy and restore are running.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 9, 2011 at 9:47 am
Is that still true if you restore with no recovery? I recently migrated from SQL 2000 and 2005 to 2008. I was able to log ship as long as it was norecovery and bring them online/standby as part of the migration.
March 9, 2011 at 10:25 am
Yes. It works, but it's up-version only.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 14, 2011 at 2:40 am
thanks guy i discover that the jobs were not runing and I'm investigating that .
but i had another problem on the other boxes which is
"Msg 32018, Level 16, State 1, Procedure sp_MSlogshippingsysadmincheck, Line 43
Log shipping is not installed on this instance"
any help will be appreciated
March 18, 2011 at 4:26 am
what "other boxes" are you referring too
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
March 18, 2011 at 4:46 am
sql server 2008 Box.
thanks for your assistance
March 21, 2011 at 1:28 pm
I had experienced similar issue while trying to log shipping sql2000 DB onto a SQL 2005 instance. Although job history shows successfully running. Actual restore wouldn't take place. Check SQL server logs on the secondary Server & verify whether if it has restored any logs or not?
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply