Mirrored Databases disconnect and goes in-recovery state after a server restart | SansSQL

Wednesday, May 7, 2014

Mirrored Databases disconnect and goes in-recovery state after a server restart

Recently, I had a situation where a production server was restarted and soon after the restart we found that the database mirroring was disconnected.
And as a bonus, one of the mirrored database was hung in recovery state.

When I investigated further, I found the below message in the SQL Server Logs.

Bypassing recovery for database '<DB Name>' because it is marked as an inaccessible database mirroring database. A problem exists with the mirroring session. The session either lacks a quorum or the communications links are broken because of problems with links, endpoint configuration, or permissions (for the server account or security certificate). To gain access to the database, figure out what has changed in the session configuration and undo the change.

This clearly says the connection between the principal and  the mirror is not established properly and the combination of a Mirrored Database with a big log file and a server restart caused the "In Recovery State" of the mirrored database.
To fix this error, I had to Restart the Database Mirroring Endpoint.

--To Stop the Endpoint

--To Start the Endpoint


yea said...

where you had this situatiion sir?//?

yangamuniprasad said...

Today i learn very interesting point and easy fix.

Unknown said...

Top 10 Casino Apps - Casinoworld
In this section we'll walk you through our selection of top casino poormansguidetocasinogambling apps, and hopefully you'll find plenty of useful information on the top How do you ventureberg.com/ use PayPal?Are there 1등 사이트 any deposit bonuses at your septcasino.com casino?

Post a Comment