Introduction
Recently, my engagements were related to SQL and 2 of which were to build SQL failover clusters on based on Windows 2008R2/SQL 2008R2 SP1 and Windows 2012/SQL 2012 SP1. In this post, I will share with you my SQL Server 2012 Failover clustering experience.
Context
As displayed in the figure below,
- The demo cluster has 2-nodes and uses File Server (FS) (Windows 2012) as storage and
- Each node has at least 2 NIC - one for internal (LAN) and for private (heartbeat) network
- FS provide 4 disks that are
- Q: used for Quorum or witness disk (1GB)
- E: used for Microsoft Distributed Transaction Coordinator (MSDTC ) (2GB)
- I: used for SharePoint 2013 Content databases (30GB), yes, it is low, but I can afford only this much:) in my local.
- H: used for Custom .NET application's databases (30GB)
![clip_image001[4]](http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-79-57-metablogapi/4186.clip_5F00_image0014_5F00_thumb_5F00_3A4CCFEF.jpg "clip_image001[4]")
Figure1: Windows Server 2012 failover cluster used in the demo
Please note that this is for demo purposes and built in my local environment (Windows 2012, Hyper 2012). My assumptions are:
- SQL database instances will need database engine feature only and no BLOB type of record expected.
- The pre-requisites for Windows and SQL failover clustering (storages, network configurations, user accounts, etc.) are already conducted.
How-to Build SQL 2012 Failover Cluster Steps
Step # | Screen capture |
1- Start your SQL 2012 Server installation media and Click 'Installation' |
|
2. Click 'New SQL Server failover cluster installation' |
|
3. OK |
|
4. Provide PK then Next |
|
5. Accept License Agreement (and the other check if you would like). Then Next |
|
6. Click Next (No worry, my VM not connected to Internet. Or you could uncheck 'include SQL Server prod… checkbox ) |
|
7. Setup Support Rules Wait for Rules check. Once done make sure no failed task. Evaluate warnings for your environment (remember the VM is not connected to Internet). Then click Next |
|
8. Next |
|
9. Select Features then Next |
|
10. Make sure feature Rule check complete with no Failed status. Then Next |
|
11. Provide Network and Instance names. The SQL cluster name is CSQLP and my database instance name is WSSDB. MS recommends use of named instances. Then Next |
|
12. Next |
|
13. Next |
|
14. Select Disk needed for the resource group (RG). Then Next |
|
15. Enable IP4 and provide IP address for this RG. Then Next |
|
16. MS recommends to use unique service accounts per each data services. Provide Service Accounts (and Collation if different than default - SQL_Latin1_General_CP1_Cl_AS). Then Next |
|
17. Click on 'Add Current User' button. Then click on Data Directories tab menu item. I use 'I' labeled clustered disk for WSSDB content. Please consider having different disks for data, log and temp data. Then Next |
|
18. Check the sharing error reports with MS if you would like. Then Next |
|
19. Make sure no clusters rules failed. Then Next |
|
20. Confirm the selection (last chance to edit before installation). Then Install |
|
21. Enjoy your waiting with a coffee. Success! Click Close to complete the process. You should see it is reflected on Cluster roles. |
|
![clip_image002[4]](http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-79-57-metablogapi/4812.clip_5F00_image0024_5F00_thumb_5F00_3CC5DBE0.png "clip_image002[4]")
![clip_image003[4]](http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-79-57-metablogapi/3414.clip_5F00_image0034_5F00_thumb_5F00_21AD0CD2.png "clip_image003[4]")
![clip_image005[4]](http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-79-57-metablogapi/5657.clip_5F00_image0054_5F00_thumb_5F00_6866800F.png "clip_image005[4]")
![clip_image006[4]](http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-79-57-metablogapi/7217.clip_5F00_image0064_5F00_thumb_5F00_2CC6714F.png "clip_image006[4]")
![clip_image007[4]](http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-79-57-metablogapi/5141.clip_5F00_image0074_5F00_thumb_5F00_315C7C09.png "clip_image007[4]")
![clip_image008[4]](http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-79-57-metablogapi/4174.clip_5F00_image0084_5F00_thumb_5F00_6F0963C5.png "clip_image008[4]")
![clip_image009[4]](http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-79-57-metablogapi/2425.clip_5F00_image0094_5F00_thumb_5F00_739F6E7F.png "clip_image009[4]")
![clip_image010[4]](http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-79-57-metablogapi/0743.clip_5F00_image0104_5F00_thumb_5F00_63B029BB.png "clip_image010[4]")
![clip_image011[4]](http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-79-57-metablogapi/1732.clip_5F00_image0114_5F00_thumb_5F00_736FBEBF.png "clip_image011[4]")
![clip_image012[4]](http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-79-57-metablogapi/1423.clip_5F00_image0124_5F00_thumb_5F00_383BE2F4.png "clip_image012[4]")
![clip_image013[4]](http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-79-57-metablogapi/7128.clip_5F00_image0134_5F00_thumb_5F00_5639F0E8.png "clip_image013[4]")
![clip_image014[4]](http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-79-57-metablogapi/6786.clip_5F00_image0144_5F00_thumb_5F00_0D33CF22.png "clip_image014[4]")
![clip_image015[4]](http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-79-57-metablogapi/0743.clip_5F00_image0154_5F00_thumb_5F00_668542D4.png "clip_image015[4]")
![clip_image016[4]](http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-79-57-metablogapi/6787.clip_5F00_image0164_5F00_thumb_5F00_790DB4F4.png "clip_image016[4]")
![clip_image017[4]](http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-79-57-metablogapi/2642.clip_5F00_image0174_5F00_thumb_5F00_4922ED66.png "clip_image017[4]")
![clip_image018[4]](http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-79-57-metablogapi/3618.clip_5F00_image0184_5F00_thumb_5F00_522F78E7.png "clip_image018[4]")
![clip_image019[4]](http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-79-57-metablogapi/2555.clip_5F00_image0194_5F00_thumb_5F00_09295721.png "clip_image019[4]")
![clip_image020[4]](http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-79-57-metablogapi/1588.clip_5F00_image0204_5F00_thumb_5F00_2DDA6E98.png "clip_image020[4]")
![clip_image021[4]](http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-79-57-metablogapi/6765.clip_5F00_image0214_5F00_thumb_5F00_4BD87C8C.png "clip_image021[4]")
![clip_image022[4]](http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-79-57-metablogapi/4212.clip_5F00_image0224_5F00_thumb_5F00_02D25AC6.png "clip_image022[4]")
Conclusion
In this post, as part of SQL 2012 Server failover cluster on top of Windows 2012 Server, I have demonstrated installing SQL 2012 Server failover cluster on node 1. In my next posts, I will demonstrate how to add a second node and how to install a new named database instance to the SQL cluster. Hope you like it and stay tuned!