New answers tagged

3

Msg 19405, Level 16, State 17, Line 3 Failed to create, join or add replica to availability group 'AGName', because node 'Node3' is a possible owner for both replica 'Node3\ReadOnly' and 'Primary/Primary'. If one replica is failover cluster instance, remove the overlapped node from its possible owners and try again. This happens for two main ...


0

I found the issue after a long time. It was due to 1 million+ files in the \MSSQL\log folder. After setting up a job that cleared that folder. The failover after SP install worked fine. The solution was confirmed on both this 2008R2 cluster, and the 2012 cluster we had the same problem on.


0

I found the issue after a long time. It was due to 1 million+ files in the \MSSQL\log folder. After setting up a job that cleared that folder. The failover after SP install worked fine. The solution was confirmed on both this 2012 cluster, and the 2008R2 cluster we had the same problem on


4

You've essentially got it right. Active/Active is really just a multi-instance SQL cluster. When you install the Failover Cluster Instance (FCI) I1 on N1 of the Windows Server Failover Cluster (WSFC) you then have to run Add Node on N2 of the WSFC for I1, and vice versa for Instance I2. The SQL Server and Agent services are installed on both nodes, but ...


0

I'll answer my own question. No, there seem to be no drawback sharing same cluster between FCI instances and instances with AlwaysOn Availability groups. Thanks for you editions, help and support.



Top 50 recent answers are included