Dear all,I have setup a 2 x node WSFC with alwaysON AG (primary replica on node1, and secondary replica on node2) with synchronous commit (and manual failover).When i trigger a failover, i can see that the AG listener resource/IP will get reallocate to node2.However, I will to setup another DR site which is on another subnet and add this node into the WSFC cluster; then add this into the AG with async commit and manual failover too.However, i am abit lost in its implementation of doing so, and i hope gurus here will experience on such setup and shed some light ->q1) when adding a node (e.g. node3) from another subnet into the existing WSFC, is there any firewall port that must be open to allow the WSFC heartbeat communication between node1,node2 (local site) to node3 ?q2) i have read some multi-subnet cluster setup, and it seems like there will be 2 DNS entries with different subnet IP for each the WSFC cluster name resource as well as the AG listener resource.e.g. AGListener 192.168.1.1 - primary site subnet ip AGListener 192.168.10.1 - dr site subnet ipe.g. WinCluster 192.168.1.100 - primary site subnet ip WinCluster 192.168.10.100 - dr site subnet ipAs DNS lookup work in a round robin fashion, what will actually happen if a client lookup AGlistener and get routed to 192.168.10.1 (which is the DR site subnet) ? Will there be a AG resource created over in the DR node which will then route the request back to the primary site ?q3) can i confirm for multi-subnet cluster setup for Alwayson AG, there is no need for any shared storage nor storage replication ? I have seen google abit but most multi-subnet cluster setup are done with FCI, can anyone here share with me any setup references for multi-subnet cluster setup with alwayson AG ?Thank you so much!Regards,Noob
↧