April 17, 2007 at 11:05 am
Hi Everyone,
This morning the primary database, configured for log shipping, wasn't able to connect to the log shipping destination. Errors, as expected, were raised at both the primary and secondary site after the grace period was expired.
When arriving in the morning users weren't able to connect to the primary site. The database server was re-booted and the log shipping caught up (the log shipping destination was now visible to the primary node).
Should the primary database server be unavailable if logs cannot be shipped ????? There are sql log entries generated for the duration of the issue, so the Agent was obviously operating.
thanks for your help.
February 14, 2011 at 1:38 pm
sound like you are talking about database mirroring not log shipping
is the witness on its own box
February 14, 2011 at 1:56 pm
tew (4/17/2007)
Should the primary database server be unavailable if logs cannot be shipped ????? There are sql log entries generated for the duration of the issue, so the Agent was obviously operating..
No, not at all. What was the error the users were getting? What was in the SQL error log?
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
February 14, 2011 at 2:00 pm
There must be a glitch with SQL Server Central's notification system... I submitted this post 4 years ago.
Sorry, but I forget the details!
February 14, 2011 at 2:47 pm
tew (2/14/2011)
There must be a glitch with SQL Server Central's notification system... I submitted this post 4 years ago.
Apologies, I didn't check the date. It bubbled to the top because danschl posted a reply.
I'm normally more attentive than this.
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
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply