August 9, 2013 at 8:57 am
Setup
FCI01 – SEVER A,B,C,D Named Instance 1- Primary Replica
Preferred Nodes A and B
FCI02- SEVER A,B,C,D Named Instance 2 – Secondary Replica
Preferred Nodes C and D.
Quorum Disk- For Voting
SERVER E – DFR server holding a secondary replica.
Always On Listener – on NODE A – NAMED INSTANCE 1
FCI01 -Primary running on Node A
FCI02 – Secondary running on Node C
SERVER E – Secondary DR replica.
1 Primary 2 Secondary copies.
----------------------------------------------------------------------------------
Perform a manual Windows Failover to NODE B. The Always On Listener goes offline.
This can be resolved by reverting back to NODE A. Or failing over the listener to convert the Secondary AOG to the AOG Primary before doing the Windows failover .
Perform the windows failover the Fail to NODE B. Then fail the AOG back to Instance 1 . Always On Listener will now be running on Node B.
However if there was a hardware failure to NODE A while it was running instance 1 and the Always On Listener was using this node A. How to recover the listener as it will be pointing to Node A as it is not windows cluster aware and only recognises the node name. Databases are in SYNC Pending mode and all dbs in the AOG are not accessible.
Primary offline = Secondary offline. I know this is fixed in SQL 2014 but what is the work around?
August 12, 2013 at 2:05 am
ANBODY??
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply