Professional Documents
Culture Documents
Microsoft SQL 2016 Step by Step Two Node Cluster PDF
Microsoft SQL 2016 Step by Step Two Node Cluster PDF
Cluster
Hussain Shakir
LinkedIn: https://www.linkedin.com/in/mrhussain
Twitter: https://twitter.com/hshakir_ms
Blog: http://mstechguru.blogspot.com/
Table of Contents
Shakir is IT Consultant with over 13 years of extensive experience working with Microsoft Technologies
AD, Exchange, O365, Windows Azure, PowerShell, Skype for Business, SQL, SharePoint and Microsoft
public clouds, and providing solutions to different local & international Enterprise customers.
Shakir has been involved in Infrastructure Designing and Implementation, Virtualization, and Disaster
Recovery. Extensive hands-on experience in Core Server Infrastructure, Cloud Computing,
Virtualization/ Management and Information Protection. Analysis and Support of Microsoft Windows
Server based Client / Server network, AD, Messaging, Skype for Business, SQL Always ON, Virtualization
and System Center Infrastructure Products. Shakir has various industry certifications: MCT, MCTS,
MCITP, MCSA, MCSE: Messaging, MCPS, MCSE: Cloud Platform and Infrastructure and also providing
trainings on Microsoft Based Technologies.
Product Overview
SQL Server 2016 delivers mission critical performance across all workloads with in-memory built-in,
faster insights from any data with familiar tools, and a platform for hybrid cloud enabling organizations
to easily build, deploy, and manage solutions that span on-premises and cloud.
SQL Server 2016 is the biggest leap forward in the Microsoft data platform history with real-time
operational analytics, rich visualizations on mobile devices, built-in advanced analytics, new advanced
security technology, and new hybrid cloud scenarios.
This document is purely written for everyone who wanted to setting up Microsoft SQL Server 2016 in
Cluster mode and those who are in process of setting up Microsoft SharePoint Server 2016 with backend
SQL 2016 2 Node Cluster with shared storage.
Lab Setup
This lab setup is based on Virtualized environment with ESX 6.0, so basic knowledge is required to setup
this lab in the same Virtualized environment. This can also be achieved by setting up the same in Hyper-
V. Table 1.1 is providing complete information about the Virtual Machines names, Network Cards,
IP/Subnet mask, and Replication Network.
Note: - You can use minimum storage for testing and lab purpose but for production environment you
have to look into the data growth in your organization and plan the storage requirement accordingly.
Drive 1, Drive 2 and Drive 3 are two LUNs which are physically connected with both SQL Virtual
Machines.
Partitions Layout
After mapping physical LUNs you can see the RAW partitions in each SQL VM disk management and
will be able to create your own partition as per the requirements. Same partition table will be appeared
in 2nd SQL Server VM.
Network Properties
You use an access point to administer a failover cluster or to communicate with a service or application
in the cluster.
You can view this report in details and can save for reference.
At this point you can see the cluster settings, disk, network and IP.
When the Windows Failover Cluster (WFC) is initially configured a Cluster Name object (CNO) will be created.
The CNO is visible as a computer object in your Activity Directory Users and Computer snap-in (dsa.msc). By
default, the CNO will be created in the Computers container and granted specific permissions:
When the SQL Server Network Name is first brought online during the FCI installation process, the CNO identity
is used to create the VCO (as long as the VCO doesn’t already exist). If the required permissions are not granted
to the CNO, the creation of the VCO will fail and so will your SQL Server FCI installation.
*Note: The Create Computer objects right only applies to Domain Functional Levels above Windows Server 2003.
For Windows Server 2003 the required privilege is “Add Workstations to the Domain”.
We must grant the permissions "Read all properties" and "Create Computer objects" to the CNO via the
container. Here’s an example of granting the required permissions for demonstration purposes:
5. Select the cluster name which was created before in Active Directory Computer Objects, and click OK.
1. Ensure that you are logged in as a user that has permissions to create computer objects in the domain.
4. Right click the OU/Container you want the VCO to reside in and click “New” -> “Computer”
We will create a computer object and assign required permission to this object which will later use in SQL Server
2016 installation as SQL Server Network Name.
6. Right click on the on the VCO you just created and select “Properties”. Click the security tab and then click
“Add”
7. Enter the CNO (Make sure to select “Computers” option in the “Object Types” window) and click “OK”.
8. Highlight the CNO, check the following permissions, and click “OK”.
Read
Allowed To Authenticate
Change Password
Receive As
Reset Password
Send As
Validate write To DNS Host Name
Validate Write To Service Principle Name
Read Account Restrictions
Write Account Restrictions
Read DNS Host Name Attributes
Read MS-TS-GatewayAccess
Read Personal Information
Read Public Information
*Note: You can replace step #8 by giving the CNO “Full Control” over the VCO
Installation of SQL Server 2016 Failover Cluster
At this point you need to move forward for the installation of SQL Server 2016 in failover mode. So let’s
start installing SQL Server 2016 in Failover Mode. Start from Node 1.
At this point we have successfully installed first Node of SQL Server 2016 in Failover Cluster Mode by
using shared storage for Database logs and temp.
With the SQL Server 2016 release Microsoft split out the installation of SQL Server Management Studio
from the main installation of SQL Server. So we need to install the management tool separately from the
same setup screen from where we started the installation steps.
The option on the SQL Server 2016 Installation Center takes you to a web download. You can also
download the SQL Server at Download SQL Server Management Studio (SSMS). After the download has
completed you can run the installation standalone without a connection to the Internet. You can see the
new SSMS 2016.
After restart open SQL Server 2016 Management with Server Network Name we configure during SQL
Installation in Active Directory.
You will connect with SNN which is created in AD and later used in SQL Server 2016 installation as shown
above.
We successfully connect with Node 1 from SQL Server Network Name.
At this screen you can see the Node 2 is going to be added in existing cluster of SQL Servers.
At this point we have successfully complete Two Node SQL Server 2016 Installation. SQL Server
Management SSMS 2016 process of installation will remain same on Node 2. You can follow steps above
as we have installed SSMS 2016 on Node 1.
This Two Node Cluster will help you to setup in your Lab environment as well as production environment
with desired storage and computing requirements. This is also suitable for SharePoint 2016
implementation and deployments.
You can see in the last snapshot that both Nodes are connected with SQL Server Network Name.
I hope you will enjoy the smooth process of this Step by Step Two Node SQL Server 2016 Deployment.
What’s Next: -
I will use the same SQL Server 2016 Cluster for the installation of SharePoint 2016 Enterprise Edition
soon