July 16, 2017 at 7:50 pm
Hi All,
We did fail over on one of our servers in production .
There was an issue , it wouldn't let me failover as it wassaying that the databases weren't synchronized
I had to pause the mirroring, thenstart it again. I waited for 5 minutes and hit refresh and it then said thedatabases are fully synchronized . Db was in Principal state .
But the next day this db goes backinto Mirror state which is supposed to be in Principal state ,
How could this happen ?
Any feedback is much appreciated
Cheers
July 18, 2017 at 11:46 am
Are you using a witness sever? If so it may have been unable to reach the primary and caused the failover.
July 18, 2017 at 5:42 pm
Joe Torre - Tuesday, July 18, 2017 11:46 AMAre you using a witness sever? If so it may have been unable to reach the primary and caused the failover.
no I don't use witness server at all ...
July 21, 2017 at 6:48 am
WhiteLotus - Sunday, July 16, 2017 7:50 PMHi All,
We did fail over on one of our servers in production .
There was an issue , it wouldn't let me failover as it wassaying that the databases weren't synchronized
I had to pause the mirroring, thenstart it again. I waited for 5 minutes and hit refresh and it then said thedatabases are fully synchronized . Db was in Principal state .
But the next day this db goes backinto Mirror state which is supposed to be in Principal state ,
How could this happen ?
Any feedback is much appreciated
Cheers
is another admin moving the mirror session maybe
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply