Installing and Configuring a Multi Subnet SQL Server (2012 and higher) Failover Clustered Instance

SQL Server 2012 (and higher) natively supports multi-subnet/geographically dispersed clusters. In this video, we will build a 2-node SQL Server 2012 failover clustered instance that spans across multiple geographical locations. We will also look at the different network configurations that need to be considered to achieve our recovery objectives and service level agreements.
This video is a part of an in-depth online course: Windows Server Failover Clustering (WSFC) for the Smart SQL Server DBA.
For more information, visit www.LearnSQLServerHADR.com
If you want to watch more videos about SQL Server high availability and disaster recovery, do yourself (and me) a favor and subscribe to my CZcams channel right here:
bit.ly/29rOqLy
And if you want to get even MORE great free content (just like this), make sure you sign up on my mailing list.
That's where I share exclusive tips that I never reveal publicly or on CZcams:
Sign up here: www.EdwinMSarmiento.com

[@kwt7667g]

Excellent explanation. A teacher at work!

[@m.mohankumar2183]

Very useful sir

[@sherly1833]

Thank you very much

[@quangphan5911]

Thank you Edwin, do you know for switching from an existing setup with single subnet to a multi-subnet setup, do you know if we can simply run the wizard to update the subnet and IP? do you have an article that talk about this?

[@EdwinMSarmiento]

It's just a matter of adding another virtual IP address to the failover cluster virtual network name.

[@quangphan5911]

@@EdwinMSarmiento Thank you, to clarify we have a 2 nodes failover cluster setup on one subnet and I'm looking to move one of the node to a new and separate subnet.

[@EdwinMSarmiento]

@@quangphan5911 I think a more important question that you need to ask is "WHY" instead of "HOW".

[@aguafria9565]

Hello Edwin, I appreciate the videos you make on SQL. I am not using the exact same setup as you are here, but I am still in a multisubnet/domain setup. I have open ports between all my servers but while the cluster is forming I get an error 'ConnectRemoteCluster (877): Couldn't resolve RPC binding to cluster 'fqdn', Status = 1753'. I am stumped here, I've already setup MSDTC with no-authentication and confirmed port 135 is open. Any ideas?

[@EdwinMSarmiento]

Start by disabling any firewall between the servers and re-run the Create Cluster Wizard. If this succeeds, then, you now have an idea what the problem might be

[@aniseto]

Wich Storage Replication system/software did you use ?

[@EdwinMSarmiento]

I used StarWind Virtual SAN to emulate storage replication between failover cluster nodes. SIOS DataKeeper is another alternative for you to test this out.

[@tsacc3813]

I have a 2 node multi subnet sql cluster everything was installed and configured successfully but am not able to connect to sqlcluster from the other node...like if sql services is running on node1 i am unable to connect the cluster by its network name from ssms from node2 and vice versa...its only connecting on the node were the sql services are running...any idea why?

[@EdwinMSarmiento]

This requires more than a simple response on a comment. There are so many things going on in a multi-subnet cluster configuration to identify what exactly is preventing this