I am planning to create FCI + HA solution in the same datacenter, but running into some problems. I'd really appreciate if someone can provide some guidance.
Here is the current configuration (All nodes are in same datacenter, Win 2012 R2, SQL 2012):
WINCluster1 SQL1 - Part of FCI instance SQLFCI1 (S drive for data, L drive for log, Q drive for quorum) SQL2 - Part of FCI instance SQLFCI1 (S drive for data, L drive for log, Q drive for quorum)
The above is a standard SQL FCI cluster and it works great.
SQL3 - Standalone box for HA (Separate S drive for data, separate L drive for log, No Q drive)
I added SQL3 to WINCluster1 and setup Node Majority for quorum (Removed Q drive disk witness from quorum) as I have odd number of nodes.
I removed SQL3 from possible owner for SQLFCI1.
Then, I setup AlwaysOn Availability Group AG1, with SQLFCI1 as Primary replica and SQL3 as secondary replica. The setup is Asynchronous with Manual failover and readable secondary.
When I use SSMS to failover between SQLFCI1 and SQL3 (back and forth), it works fine. When I use FCI under WinCluster1 to failover between SQL1 and SQL2 for SQLFCI1, it works fine.
But, when I shutdown SQL1, the SQLFCI1 fails over to SQL2, which is perfect, but SQL3 goes offline. I can remote into SQL3, click on drives, etc, but the cluster resources goes offline.
Same thing happens when my network engineer unplugs NIC cards, simulating NIC fail scenario, from SQL1. And both cases happens when SQL1 is online but SQL2 is down or NIC unplugged.
Here is the error message under event viewer: "The cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk."
And another strange thing is, when I shutdown both SQL1 and SQL2, under WinCluster1, the current owner for SQLFCI1 says SQL3, even though there is nothing shared between SQL3 and SQL1, SQL2. SQL3 is just standalone box. It brings down the Windows cluster and nothing works. Once SQL1 and SQL2 come up, it starts working.
Hope this explains the current configuration and issue. Thank you so much for your assistance in advance.
Have a wonderful day.