1. Greg Seidel Technology Specialist – SQL Server
SQL Server 2008 R2 Failover Clustering
Rolling Upgrade
Greg Seidel Technology Specialist – SQL Server

2. Session Overview
Enhancements in SQL Server 2008 R2 Failover Clustering
Installation Options
Rolling upgrade
Known Issues

3. Enhancements in SQL Server 2008 R2 Failover Clustering
Reliable Setup Experience
Simplified installation process by removing remote installation (no Task Scheduler)
Integrated OS and SQL Server checks
MSDTC
Allows selecting multiple drives
Full-text and replication installed as part of the database engine
Hot add storage

4. Enhancements in SQL Server 2008 R2 Failover Clustering
Rolling Upgrade and Patching
Made available for the first time in 2008
Significantly increases availability
In various client tests, in-place rolling upgrade to SQL 2008 R2 cluster incurred approx 2 to 3 minutes downtime.

5. Enhancements in SQL Server 2008 R2 Failover Clustering
High availability with Add/Remove Node Operations
Add/Remove node operations are performed on the node that is being added/removed
Does not affect the node on which SQL is running
Enable slipstream installation
Available with SQL 2008 SP1
You can slipstream a SP and CU with the RTM to simplify and speed up deployments

6. Integrated with Windows 2008
Enhancements in SQL Server 2008 R2 Failover Clustering
Integrated with Windows 2008
Service SIDs remove the requirement of domain groups during setup
DHCP, IPv6, and iSCSI are supported
Supports up to 16 node clusters for SQL Server Enterprise edition
Windows Server features not supported by SQL
Installation on Windows Server Core
Separate subnets for cluster nodes
Stretch clustering is available similar to 2005

7. Installation Options Integrated Installation
Create and configure a single-node SQL cluster
Run add node on each additional cluster node
Advanced/Enterprise Installation
Prepare – install binaries and files on each node of the cluster. Do not bring individual nodes online
Complete - Once all preparations are complete, nodes are combined and cluster is brought online

8. SQL Server 2008 Integrated Cluster Install with Add Node
4/23/2018
Windows Server Failover Cluster
SQL Server
Failover Cluster
Integrated
Install
Node1
Add Node
Node2
Add Node
Node3
Add Node
Node4
© 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

9. SQL Server 2008 Integrated Cluster Install with Add Node
Number of Installs Required
SQL Server 2008
1 Instance
2 Instances
3 Instances
4 Instances
2 nodes 2 4 6 8
3 nodes 3 9 12
4 nodes 16
5 nodes 5 10 15 20
6 nodes 18 24
7 nodes 7 14 21 28
8 nodes 32

10. SQL Server 2008 Integrated Cluster Install with Add Node (3)
Using Command Prompt
Install a single-node SQL Server failover cluster with the Database Engine
setup.exe /q /ACTION=InstallFailoverCluster /FEATURES=SQL /INSTANCENAME="<Insert Instance Name>" [/INSTANCEIDSUFFIX="<Insert InstanceID Suffix>"] /INSTANCEDIR="C:\Program Files\Microsoft SQL Server" /INSTALLSHAREDDIR="C:\Program Files\Microsoft SQL Server" /SQLSVCACCOUNT="DomainName\UserName" /SQLSVCPASSWORD="XXXXXX" /AGTSVCACCOUNT="DomainName\UserName" /AGTSVCPASSWORD="XXXXXX" /SQLDOMAINGROUP="DomainName\DomainGroup" /INSTALLSQLDATADIR="<Drive>:\<Path>\MSSQLSERVER" /SQLCOLLATION="CollationName"; default is SQL_Latin1_General_CP1_CS_AS" /FAILOVERCLUSTERGROUP="<Insert new Cluster Group name>" /FAILOVERCLUSTERDISKS="<Cluster Disk Resource Name - for example, 'Disk S:'" /FAILOVERCLUSTERIPADDRESSES="IPv4;XXX.XXX.XXX.XXX;Local Area Connection;xxx.xxx.xxx.x" /FAILOVERCLUSTERNETWORKNAME="<Insert Failover Cluster Instance Name>" /SQLSYSADMINACCOUNTS=" DomainName\UserName " [/SECURITYMODE=SQL /SAPWD="StrongPassword"]
Note
IPv4;XXX.XXX.XXX.XXX  requires the IP address
Local Area Connection;xxx.xxx.xxx.x  requires subnet mask for public network
Add a node to an existing failover cluster instance with the Database Engine
setup.exe /q /ACTION=AddNode /INSTANCENAME="<Insert Instance Name>" /SQLSVCACCOUNT="<SQL account used on other nodes>" /SQLSVCPASSWORD="<password for SQL account>" /AGTSVCACCOUNT="<SQL Server Agent account used on other nodes>", /AGTSVCPASSWORD="<SQL Server Agent account password>“ /INDICATEPROGRESS

11. SQL Server 2008 Advance Cluster Install
Enterprise Deployment Option
SQL1
Phase 1 : Prepare
On all the nodes that are going to be in the SQL Server cluster, run setup and use “Prepare” option.
Use same InstanceID\InstanceName on all nodes
Prepared instances will not be usable until the installation process is “completed” in Phase 2.
Phase 2 : Complete
On the node that is the owner of the shared disk, run setup and use “Complete” option.
SQL Server setup will form the SQL Server failover cluster and join all the prepared nodes for the selected instance as a cluster.
FC1

12. SQL Server 2008 Advance Cluster Install
Using Command Prompt
"Preparation" step of a failover cluster advanced installation scenario for the Database Engine
Setup.exe /q /ACTION=PrepareFailoverCluster /FEATURES=SQL /INSTANCENAME="<Insert Instance Name>" [/INSTANCEIDSUFFIX="<Insert InstanceID Suffix>"] /INSTANCEDIR="<Drive>:\Program Files\Microsoft SQL Server" /INSTALLSHAREDDIR="<Drive>:\Program Files\Microsoft SQL Server" /SQLSVCACCOUNT="DomainName\UserName" /SQLSVCPASSWORD="XXXXXX" /AGTSVCACCOUNT="DomainName\UserName" /AGTSVCPASSWORD="XXXXXX" /SQLDOMAINGROUP="DomainName\DomainGroup"
“Completion" step of a failover cluster advanced installation scenario for the Database Engine
setup.exe /q /ACTION=CompleteFailoverCluster /INSTANCENAME="<Insert Instance Name>" /FAILOVERCLUSTERNETWORKNAME="<Insert FOI Name>" /FAILOVERCLUSTERGROUP="Insert New Cluster Group>" /FAILOVERCLUSTERDISKS="<Cluster Disk Resource Name - e.g., 'Disk S:'>" /FAILOVERCLUSTERIPADDRESSES="IPv4;XXX.XXX.XXX.XXX;Local Area Connection;xxx.xxx.xxx.x" /INSTALLSQLDATADIR="<Drive>:\<Path>\MSSQLSERVER" /SQLCOLLATION="SQL_Latin1_General_CP1_CS_AS" /SQLSYSADMINACCOUNTS="DomainName\UserName" [/SECURITYMODE=SQL /SAPWD="StrongPassword"]
Note: IPv4;XXX.XXX.XXX.XXX = IPv4; (this is the IP address)
Local Area Connection;xxx.xxx.xxx.x =Public; (this is the subnet mask)

13. Rolling Upgrade Process
Install pre-requisites on all passive nodes
.Net Framework 3.5 SP1 (except for Windows 2003 IA64; install .Net Framework 2.0 SP2
MSI 4.5
Windows hotfix requirement for Filestream on Windows Server 2003 SP2 for clustered engine installations. KB
Pre-requisites require reboot. Reboot passive nodes
Upgrade passive nodes
Once more than 50% of nodes are upgraded
Setup automatically initiates a failover to one of the upgraded nodes
Upgrade scripts are run at startup on the upgraded node
Total downtime taken is time to failover to upgraded node (approx 15 secs) plus time taken to run upgrade scripts 2-3 mins
Upgrade remaining nodes

14. SQL Server 2008 R2 Rolling Upgrade
Prepare to Upgrade (SQL1 instance)
SQL1
SQL2
SQL1 Possible Owners
Consider a 4 nodes cluster: Node 1, Node 2, Node 3 and Node 4. SQL Server 2005 instance SQL1 is currently active on Node 1.
Rolling upgrade steps for upgrading SQL1 instance from SQL Server 2005 to SQL Server 2008 R2:
To reduce downtime and number of reboots, consider installing the following on passive nodes
.NET 3.5 SP1 (for all platforms except for IA64. On IA64, install .NET 2.0 SP2)
Important: XPS driver takes the cluster service down on the current node
.Net3.5SP1 installer might pop up a message telling to close another existing .Net3.5 installer. Hit “Ignore” and installer should continue successfully.
MSI 4.5 (appears as KB – v2)
Windows hotfix requirement for Filestream on Windows Server 2003 SP2 for clustered Engine installations: Windows KB
Updated SQL Server 2008 R2 Setup Support Files (not required but recommended)

15. SQL Server 2008 R2 Rolling Upgrade
Upgrade Step 1
SQL1
SQL2
SQL1 Possible Owners
SQL1 Upgraded Nodes
Upgrade half of the nodes. To minimize failover start upgrading passive nodes first
Run Upgrade on Node 4
Take Node 4 out of possible owners for SQL Server network name
Upgrade Node 4 bits
Run Upgrade on Node 3
Take Node 3 out of possible owners for SQL Server network name
Upgrade Node 3 bits
Note: Numbered steps are user actions and lettered steps are handled by setup internally.
At this point Node 1 and Node 2 are only nodes in possible owners for SQL Server network name and 50% of the nodes (Node 3 and Node 4) have been upgraded
Consider moving other instances (SQL2) to avoid service restart.

16. SQL Server 2008 R2 Rolling Upgrade
Upgrade Step 2
SQL1
SQL2
SQL1 Possible Owners
SQL1 Upgraded Nodes
Run Upgrade on Node 2
Add Node 3 and Node 4 to possible owners for SQL Server network name
Remove Node1 and Node 2 from possible owners for SQL Server network name
Cause failover of SQL1 to either Node 3 or Node 4. The first time the SQL1 Engine starts, as part of Engine startup it will detect whether it needs to run upgrade scripts and run them as necessary.
Upgrade Node 2 bits
Add Node 2 to possible owners for SQL Server network name
Note: Numbered steps are user actions and lettered steps are handled by setup internally.

17. SQL Server 2008 R2 Rolling Upgrade
Upgrade Step 3
SQL1
SQL2
SQL1 Possible Owners
SQL1 Upgraded Nodes
Run Upgrade on Node 1
Upgrade Node 1 bits
Add Node 1 to possible owners for SQL Server network name
Note: Numbered steps are user actions and lettered steps are handled by setup internally.

18. How to Control Failover During Rolling Upgrade
Command line parameter:
/FAILOVERCLUSTERROLLOWNERSHIP=0 | 1 | 2
There is NO option to control failover on UI. To control failover on UI, run setup on command line by supplying the failover option (UI uses the command line setting supplied):
setup.exe /FAILOVERCLUSTERROLLOWNERSHIP=…
/FAILOVERCLUSTERROLLOWNERSHIP=0
Do not roll cluster ownership to the upgraded nodes.
Do not add this node to possible owners of the SQL Server cluster at the end of upgrade of this node.
Note: this is not an option after the ownership has already transferred.
/FAILOVERCLUSTERROLLOWNERSHIP=1
Roll cluster ownership to the upgraded nodes (if this has not happened already).
Add this node to possible owners of the SQL Server cluster at the end of upgrade of this node.
/FAILOVERCLUSTERROLLOWNERSHIP=2
This is the default setting.
This setting indicates that SQL Server setup will manage the cluster ownership as needed.

19. SQL Server 2008 R2 Rolling Upgrade
Rolling Upgrade steps on a two node Cluster
Run Upgrade on Node 2 (passive node)
Takes Node2 out of possible owners for SQL Server network name
Upgrade Node2 bits
At this point Node1 is only node in possible owners for SQL Server network name and 50% of nodes have upgraded
Run Upgrade on Node1
Add Node2 to possible owners for SQL Server network name
Remove Node1 from possible owners for SQL Server network name (will cause failover to Node2)
Upgrade Node1 bits
Add Node1 to possible owners for SQL Server network name

20. Rolling Patch Upgrade
Rolling patch and Service Pack with minimal downtime for SQL 2008 R2
Manual Process:

21. Known Setup Issues Issue Fixed In KB
When you install a clustered instance of SQL Server 2008, account validation fails even though you have specified the correct domain account and password
CU#1
955948
Error message when you try to add a second node to a SQL Server 2008 failover cluster: "The current SKU is invalid"
957459
The CompleteFailoverCluster action does not detect the correct SKU that is prepared by using the PrepareFailoverCluster action in SQL Server 2008
957806
Cluster upgrade to SQL Server 2008 fails when SQL Server 2005 cluster nodes have different installed features
955949
A new node is not added to a SQL Server 2008 Analysis Services cluster or a SQL Server 2008 Reporting Services cluster if the SQL Server 2008 Database Engine is not installed
957807
You receive a warning about the network binding order on the Setup Support Rules page when you install SQL Server 2008 in a failover cluster
Active
955963
Note: The above setup issues are fixed in Cumulative Update 1 (CU#1) for SQL Server You can proactively avoid known setup issues by doing a slipstream installation of SQL Server 2008 RTM + SP + CU

22. Questions?