Principal Disconnected, In Recovery... on both servers after restart

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2008 » SQL Server 2008 High Availability » Principal Disconnected, In Recovery... on...

Principal Disconnected, In Recovery... on both servers after restart

Rate Topic

Display Mode

Topic Options

Author

Message

Jetro

Posted Wednesday, December 08, 2010 5:21 PM

Old Hand

Group: General Forum Members
Last Login: Wednesday, September 21, 2011 8:24 AM
Points: 369, Visits: 377

Hi,

today I had the problem, that after a restart of my two mirrored database servers on both servers all databases where in the state "Principal, disconnected, in recovery". So both databases weren't available.

We "fixed" this with "ALTER DATABASE XXX SET PARTNER OFF" to bring the database back online...

Did you ever saw this behaviour and know a better solution than removing the mirroring session from the database?

Thanks in advance!

-----------------------
SQL Server Database Copy Tool at Codeplex

Post #1032231

SQLBalls

Posted Thursday, December 09, 2010 9:05 AM

Old Hand

Group: General Forum Members
Last Login: Tuesday, May 21, 2013 1:34 PM
Points: 385, Visits: 611

I had this happen once, but when I tried to replicate it in a dev environment to try to trouble shoot it, I could not force it to repeat.

I was in HSHA, mirroring is supposed to prevent split brain issues like this from happening, but that is exactally what I did, recovered one set of databases and re-initialized mirroring.

What is the build version of your 2008 server, sp1, sp2, sp1 & some CU's. There was an issue with the way the transactions were passed along in mirroring that could cause mirroring to enter a suspended state, that was fixed in CU 5 for sp1 that we applied, but this is completely seperate from the issue you are posting about.

If your running SP 2 it would have been fixed in there as well.

Twitter: @SQLBalls
Blog: http://www.SQLBalls.com

Post #1032512

ALZDBA

Posted Thursday, December 09, 2010 9:20 AM

SSCertifiable

Group: General Forum Members
Last Login: 2 days ago @ 2:17 AM
Points: 6,862, Visits: 8,049

You should first have looked in your sqlserver errorlog.
- what topology of mirroring were you using ?
- did you have a look at your SQLServer ERRORLOG file ?
- did you find related messages ?

- are you capturing dbmirroring events you all your instances ?

Please post your @@version info.

Johan

     Jul 13

Don't drive faster than your guardian angel can fly ...
but keeping both feet on the ground won't get you anywhere w00t

- How to post Performance Problems
- How to post data/code to get the best help

- How to prevent a sore throat after hours of presenting ppt ?

"press F1 for solution", "press shift+F1 for urgent solution" BigGrin

Need a bit of Powershell? How about this

Who am I ? Sometimes this is me but most of the time this is me Hehe

Post #1032529

gianmh

Posted Thursday, October 04, 2012 12:49 PM

Forum Newbie

Group: General Forum Members
Last Login: Thursday, February 14, 2013 12:45 PM
Points: 8, Visits: 97

Thank you so much, I had stuck production server

Post #1368644

d-i-m-on

Posted Tuesday, October 30, 2012 9:45 AM

Grasshopper

Group: General Forum Members
Last Login: Friday, April 26, 2013 2:53 PM
Points: 11, Visits: 232

I was helped by the following: DROP\CREATE Mirroring Endpoint on Mirror Serser.

Post #1378862

Perry Whittle

Posted Wednesday, October 31, 2012 4:19 AM

SSCertifiable

Group: General Forum Members
Last Login: Today @ 10:32 AM
Points: 5,204, Visits: 11,159

normally stopping and restarting the endpoints will cure the issue

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" Wink

Post #1379224

« Prev Topic | Next Topic »

Permissions