December 11, 2014 at 5:50 am
I have 20 databases mirrored from A to B.
I shut down A, 18 come up at B, 2 don't.
1 is is mirror, disconnected, restoring.
2 is in mirror, disconnected, in recovery.
The question is why and what to do to resolve this issue.
This is a test and we don't want data loss.
Appreciate any answers.
December 11, 2014 at 5:57 am
Everything I'm reading points to connection type issues / endpoints etc. but I can't explain this at the database level?
December 11, 2014 at 8:51 am
are these all on the same servers?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
December 15, 2014 at 1:20 am
Hi,
Have you checked the error log. Looks like a resource issue on the mirror. we had a similar issue where the mirror was low and memory and the database was stuck at in recovery state
December 15, 2014 at 5:04 am
Sorry for the delay ... and thanks for the replies. No, they were on different servers at different locations. I'm at a loss to explain it. There are log entries re: loss of comms and this is a busy database but still.
Update - Once I brought the previous principal back up, and switched back, the busiest database just got 'stuck' in sycnhronizing. I've been monitoring the lsns and there's no progress so I'm going to break and re-establish.
December 15, 2014 at 5:09 am
Have you checked the state of the mirror endpoints? As a matter of course I would restart them.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
December 15, 2014 at 5:43 am
Thanks. I don't fully understand what restarting the end points does. Could it affect any of my other correctly mirroring live DBS?
December 15, 2014 at 5:59 am
snomadj (12/15/2014)
Thanks. I don't fully understand what restarting the end points does. Could it affect any of my other correctly mirroring live DBS?
So you have multiple Principal servers?
Are all the databases that are causing an issue on the same instance?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
December 15, 2014 at 6:04 am
No sorry perhaps I've not been clear. 1 principal. 1 mirror. 70 DBS. 68 switched roles correctly when principal SQL instance was switched off. When original SQL principal instance restarted 69 switched back correctly once manually failed over. 1 is left in synchronising. I can work around (as in remirror) but it's unnerving that our ha solution didn't work and were not sure why.
December 15, 2014 at 9:24 am
Can you post the results of the following, replace "yourdb" with the name of the principal database names that have the issue
SELECTDB_NAME(database_id)
, mirroring_safety_level_desc
, mirroring_witness_state_desc
FROM [sys].[database_mirroring]
WHERE database_id IN (DB_ID('yourdb'),DB_ID('yourdb'),DB_ID('yourdb'))
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply