Hi,I was wondering if anyone was able to help with a problem I am experiencing with the failback of SQL Server 2014/Windows Server 2012 R2 FCI that is part of an Availability Group[b]Overview of the set up:[/b]3-node WSFC (Windows 2012 R2), 2 nodes within same datacenter and the other node in a second datacenter.The 2 nodes in the same datacenter are configured as an AlwaysOn AG Replica and the node in the second datacenter is a standalone AG Replica. Currently configured as FCI (Primary) and Standalone (Secondary) with a manual failover mode and asynchronous commit availability mode.[b]Overview of problem:[/b]Failover at an Availability Group level works fine and can happily switch between primary and secondary and back again use the appropriate commands within SSMS. The problem comes by where we want to test running from the second node of the FCI. So within Failover Cluster Manager I've moved the SQL Server role from Node 1 to Node 2 and this works OK, this causes the AG role to failover as well. When I come to failback I repeat the same process but this time moving the SQL Server role from Node 2 back to Node 1 and the AG role does not move this time. I try to manually move it but fails saying the selected node is not a possible owner of the AG cluster resource.If I go into the properties of the AG cluster resource it shows only the current node (Node 2) as a possible owner. If select Node 1 as well I can then move the resource back. The problem being that this property is reset each time it fails over so only the current node is selected.Is anyone able to help provide insight into why this might be happening? I know your not supposed to control/configure AG roles through the Failover Cluster Manager as it's not aware of the synchronization state of the AG replica's but I can't see how else you would control a failover between FCI nodes.Many thanks....
↧