15
2017
Setting up Always ON Availability Group in Multi Subnet Cluster – Recommendations
While planning to configure always on availability group for first time on a multi subnet cluster found following use articles, it provides clear picture in terms of design and architecture, our requirement was to build SQL 2012 cluster on DC1 along with a reporting standalone SQL instance in same DC1, along with it, we want to have DR solution in DC2 where two standalone SQL instances are present on their respective server, to achieve this configuration following articles helped,
Following article highlights Microsoft instructions on configuring Windows multi subnet cluster for Always ON availability groups,
https://msdn.microsoft.com/en-us/library/hh781257.aspx
Below are highlighted important page numbers for easy reference,
Page number 11, this diagram talks about 1 windows cluster in 2 different subnets where the A1 and A2 are in a SQL Failover cluster and rest of the nodes A3, B1, B2 in Standalone. Exactly the same way we want it for our environment. It uses FileShare Witness as optional which is a best practice to have one.
Then refer to Page 15 to 20 to understand how Quorum voting works and how majority decide.
Link for read-only configuration of AlwaysOn can be found here https://msdn.microsoft.com/en-us/library/jj542414.aspx
Detailed ports to be opened:
However, check the article below http://dsfnet.blogspot.ca/2013/04/windows-server-clustering-sql-server.html#!/2013/04/windows-server-clustering-sql-server.html this is not a Microsoft article. Infrastructure team can always review and verify if it is correct or if we need to add or remove any from the list.
Hope this helps.

Leave a comment
Subscribe to this blog via Email
Old Posts
- November 2017 (3)
- October 2017 (4)
- September 2017 (2)
- May 2017 (1)
- April 2017 (1)
- July 2016 (3)
- May 2016 (1)
- April 2016 (1)
- February 2016 (2)
- January 2016 (1)
- October 2015 (1)
- September 2015 (1)
- August 2015 (1)
- July 2015 (2)
- June 2015 (3)
- April 2015 (1)
- March 2015 (1)
- December 2014 (1)
- September 2014 (2)
- April 2014 (1)
- January 2014 (3)
- October 2013 (2)
- September 2013 (2)
- August 2013 (4)
- July 2013 (1)
- June 2013 (2)
- May 2013 (5)
- April 2013 (3)
- March 2013 (1)
- February 2013 (9)
- January 2013 (11)
- December 2012 (14)
- November 2012 (3)
- October 2012 (4)
- July 2012 (2)
- June 2012 (3)
- May 2012 (2)
- April 2012 (8)
- March 2012 (6)
- February 2012 (3)
- January 2012 (1)
- December 2011 (5)
- November 2011 (8)
- October 2011 (5)
- September 2011 (3)
- August 2011 (3)
- July 2011 (3)
- May 2011 (1)
- November 2010 (1)
Tags
Calender
M | T | W | T | F | S | S |
---|---|---|---|---|---|---|
« Nov | ||||||
1 | 2 | 3 | ||||
4 | 5 | 6 | 7 | 8 | 9 | 10 |
11 | 12 | 13 | 14 | 15 | 16 | 17 |
18 | 19 | 20 | 21 | 22 | 23 | 24 |
25 | 26 | 27 | 28 | 29 | 30 | 31 |
View Post by Categories
Recent Articles
- Setting up Always ON Availability Group in Multi Subnet Cluster – Recommendations
- Configuring Replication with Always ON Availability Group
- Login failed for user ‘DOMAIN\COMPUTER$’. Reason: Could not find a login matching the name provided. [CLIENT: ]
- Modern Servicing Model (Service Pack and Cumulative Updates) for SQL Server 2017 and onwards
- Fix: SSMS 2012 opening Debug window when pressing F5