InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comWed, 22 May 2013 06:10:32 GMT20http://www.sqlservercentral.com/Forums/Topic1362001-1549-1.aspx[quote][b]saidapurs (10/4/2012)[/b][hr]Hi Scogeb, Database will not go off line....Thanks Satish[/quote]Incorrect, if you only have the primary and the witness and the witness goes down the principal database will go down too since quorum can no longer be established.Thu, 04 Oct 2012 01:12:35 GMTPerry Whittlehttp://www.sqlservercentral.com/Forums/Topic1362001-1549-1.aspxHi Scogeb, Database will not go off line....Thanks SatishThu, 04 Oct 2012 00:59:49 GMTsaidapurshttp://www.sqlservercentral.com/Forums/Topic1362001-1549-1.aspxyou're welcomeWed, 03 Oct 2012 11:50:45 GMTPerry Whittlehttp://www.sqlservercentral.com/Forums/Topic1362001-1549-1.aspxJust a quick update. This happened again and I tried to restart the endpoint and that worked. Thanks!Wed, 03 Oct 2012 11:32:30 GMTscogebhttp://www.sqlservercentral.com/Forums/Topic1362001-1549-1.aspx[quote][b]scogeb (9/25/2012)[/b][hr]I am going to try to restart the endpoint per Perry's suggestion next time this happens. I will post back the results at that time.[/quote]This should be your first action, post back let us know how you get onTue, 25 Sep 2012 09:17:03 GMTPerry Whittlehttp://www.sqlservercentral.com/Forums/Topic1362001-1549-1.aspx[quote][b]saidapurs (9/25/2012)[/b][hr]Hi Scogeb, Ya i have same setup & already i faced this issue. First your restart your witness server or make it up then restart primary server automatically database will come up as primary then you restart mirror server. Than you check with fail-over will work 100%...Thanks & RegardsSatish[/quote]Satish, if I'm following what you're saying, you want me to restart my witness server first? That would cause the database to go offline. Only my witness and primary(previously mirror before failover) can see each other at this point. If something happens to either of those servers, the database goes offline. I am going to try to restart the endpoint per Perry's suggestion next time this happens. I will post back the results at that time.Tue, 25 Sep 2012 08:39:16 GMTscogebhttp://www.sqlservercentral.com/Forums/Topic1362001-1549-1.aspxHi Scogeb, Ya i have same setup & already i faced this issue. First your restart your witness server or make it up then restart primary server automatically database will come up as primary then you restart mirror server. Than you check with fail-over will work 100%...Thanks & RegardsSatishTue, 25 Sep 2012 00:23:28 GMTsaidapurshttp://www.sqlservercentral.com/Forums/Topic1362001-1549-1.aspxTry restarting the mirror endpoint next time instead of the sql server serviceThu, 20 Sep 2012 16:35:53 GMTPerry Whittlehttp://www.sqlservercentral.com/Forums/Topic1362001-1549-1.aspxHello all. I have several setups with principal, mirror and witness set to High safety/auto failover. On rare occaisions, the principal will become disconnected from the witness and mirror, due to network issues on the principal. This causes a failover to the mirror which works perfectly. The problem is, I can't fail back over to the principal. In SSMS, it continues to show disconnected from the witness and mirror even though pings work both from the principal to the mirror and from the mirror to the principal. The network issue has clearly been resolved. The only way I can get the mirror and witness to be able to see the principal is to restart the SQL services on the principal. Then all works good again. Has anyone else experienced this or know what would cause something like this?Thu, 20 Sep 2012 08:09:01 GMTscogeb