Gopal Ashok Program Manager Microsoft Corp Session Code: DAT 312

Session Agenda Failover Clustering; Better together

Database Downtime Unplanned Downtime Failure Protection User Errors Planned Downtime Online Administration Predictable Resourcing Database Downtime Drivers and Clustering SQL Server Failover Clusters Instance-level HA Automatic failure detection Automatic failover SQL Server Failover Clusters Instance-level HA Automatic failure detection Automatic failover SQL Server 2008 Failover Cluster Rolling in-place upgrade with minimal downtime Rolling patch with minimal downtime Add node (at RTM+SP+CU level, all at once), with no downtime SQL Server 2008 Failover Cluster Rolling in-place upgrade with minimal downtime Rolling patch with minimal downtime Add node (at RTM+SP+CU level, all at once), with no downtime

Windows Server 2008 Highlights HCL is not needed anymore!!!! More flexible support policy for cluster hardware Any hardware configuration supported…… Components should have Windows Server 2008 R2 logo The configuration should pass cluster validation test Configuration change on an existing cluster?? Just re-run the cluster validation

Windows Server 2008 Highlights Extremely Simplified Setup

Quorum Model Node Majority: Each node that is available and in communication can vote Node and Disk Majority: Each node plus a designated disk in the cluster storage (the “disk witness”) can vote, whenever they are available and in communication. Node and File Share Majority: Each node plus a designated file share created by the administrator (the “file share witness”) can vote, whenever they are available and in communication. No Majority: Disk Only: The cluster has quorum if one node is available and in communication with a specific disk in the cluster storage. Only the nodes that are also in communication with that disk can join the cluster.

SQL Server 2008 Failover Clustering Better together with Windows Server 2008 Clustering Cluster Validation Support IPv6,DHCP and ISCSI Support 16 nodes on Enterprise Edition Multi-subnet not yet supported Resilient SQL Server Failover Cluster Setup Integrated OS cluster health checks Integrated SQL Server ® setup health checks No remote execution during setup

SQL Server ® 2008 on Windows Server ® 2008 R2 SQL Server ® 2008 RTM cluster install does not work on Windows Server ® 2008 R2 Required: SQL Server ® 2008 CU2 and above using SQL Server ® 2008 patchable setup process Recommended: SQL Server ® 2008 SP1 and above using slipstream process

Integrated Install Install local machine bits and create single-node SQL Server ® cluster in one integrated step Run Add Node on each additional node Advanced/Enterprise Install Prepare – install local machine bits first on each node Complete – combine prepared nodes and create SQL Server ® cluster as final step Failover Clustering Setup

Integrated Install Node1 Add Node Node2 Add Node Node3 Add Node Node4 SQL Server® Failover Cluster Windows Server® Failover Cluster Integrated Install

Phase 1: Prepare Failover Cluster On all the nodes that are going to be in the SQL Server ® failover cluster, run SQL Server ® setup and use “Prepare” option. These prepared instances will not be usable until the installation process is “completed” in Step 2. Phase 2: Complete Failover Cluster On one of the prepared nodes, run SQL Server ® 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. Advanced failover cluster install

Phase 1: Prepare Failover Cluster Prepare SQL Server ® failover cluster instance on each node separately Instances are not useable at the end Phase 2: Complete Failover Cluster Create a SQL Server ® Failover Cluster from cluster-prepared SQL Server ® instance at once. Instance becomes useable at the end Notes: Same InstanceID/Instance Name on all nodes Can use third-party remote deployment solution Create from multiple cluster-prepared SQL Server ® instances Advanced\Enterprise Setup

Integrated Cluster Setup

Reduce Planned Downtime Introducing: Rolling Version Upgrade and Rolling Patch Updates Install prerequisites on each passive node and upgrade the shared SQL Server components Restart passive nodes as prompted Fail over SQL Server instance to prepared node (has prerequisites and updated components) Install prerequisites on remaining passive node(s) and upgrade shared SQL Server components On each passive node, initiate engine upgrade installation process Upgrade manages failover of SQL Server instance to upgraded node based on upgraded node count Upgrade the remaining nodes Rolling Upgrade

Rolling Failover Cluster Upgrade Passive Active  Windows Server ® 2003 R2 EE SP2, 64-Bit  SQL Server ® 2005 EE SP3, 64-Bit Disk Array

Upgrade Interface Shows the upgrade state of all nodes in the cluster and the current version on the node Also indicates whether the database and replication scripts have been upgraded

Rolling Failover Cluster Upgrade Passive Active Step #1: Install Prerequisites: 1- Microsoft.Net Framework ® 3.5 SP1 2- Microsoft Windows Installer ® On Microsoft Windows Server ® 2003, QFE (KB937444) 4- SQL Server ® 2008 Setup Support files REBOOT… Step #2: Install Prerequisites: 1- Microsoft.Net Framework ® 3.5 SP1 2- Microsoft Windows Installer ® On Microsoft Windows Server ® 2003, QFE (KB937444) 4- SQL Server ® 2008 Setup Support files REBOOT … SQL Server ® Instance Manual Failover Best practice – Installation of prerequisites

Rolling Failover Cluster Upgrade Active Passive Step #4: Upgrade to SQL Server ® 2008 on Active Node Step #3: Upgrade to SQL Server ® 2008 on Passive Node Step 5: SQL Server ® Instance Automatic Failover No client connection for 1-2 minutes while db is being upgraded to SQL Server® 2008 on the left node SQL Server ® 2008 SQL Server® 2008 Active Removed from Cluster Group Possible Owners

SQL Server ® Rolling Failover Cluster Upgrade Passive Active Mirrored SQL Step #1: Note: Mirror version >= Principal version Upgrade to SQL Server ® 2008 on Mirrored Instance Step#2: Manual Failover to the database mirroring partner for each database Mirroring suspended SQL Server® 2008 SQL Server® Cluster Principal SQL Server® 2008 Mirroring resumed Step#4: Manual Failover to the database mirroring partner for each database With database mirroring

Failover during upgrade SQL Server® 2008 SQL Server® 2005 SQL Server® 2008 Start Upgrade……

Controlling Failover during upgrade Use command line for upgrade /FAILOVERCLUSTERROLLOWNERSHIP parameter controls the behavior 0 = Don’t failover; Don’t add to possible owners 1= Failover; Upgrade; Add to possible owners 2 = Default; Setup controls failover

Rolling Patching No built-in logic to do automatic failover during upgrade Plan the upgrade to ensure maximum uptime and availability Identify passive nodes to be upgraded first Remove passive nodes from possible node owner list Apply update on each passive node Add passive nodes back to node owner list Fail over SQL Server instance to an updated node Validate that SQL Server instance comes online and check version of engine for proper value Remove remaining non-updated nodes from possible node owner list Apply update on remaining non- updated passive nodes Add updated nodes back to node owner list and test failover

Rolling Patch Upgrade

Summary Windows Server 2008 and SQL Server 2008 provides a seamless experience for clustering Removes lot of the deployment and hurdles from Windows Server 2003 and SQL Server 2005 Provides a much improved setup experience, better manageability and troubleshooting infrastructure

Sessions On-Demand & Community Resources for IT Professionals Resources for Developers Microsoft Certification & Training Resources Resources Required Slide Speakers, TechEd 2009 is not producing a DVD. Please announce that attendees can access session recordings at TechEd Online. Required Slide Speakers, TechEd 2009 is not producing a DVD. Please announce that attendees can access session recordings at TechEd Online.

SQL Server ® 2008 Failover Clustering White Paper: clustering.aspx clustering.aspx Recommended Books Online Doc Refresh #7 (May, 2009), or later: Failover Clusters - Getting Started: us/library/ms aspx us/library/ms aspx Rolling upgrade process and best practice: Maintaining a Failover Cluster: us/library/ms aspx us/library/ms aspx Setup command line usage: us/library/ms aspx us/library/ms aspx Configuration.ini file usage: us/library/dd aspx us/library/dd aspx Documents and Related Content

Related Content Breakout Sessions (session codes and titles) Interactive Theater Sessions (session codes and titles) Hands-on Labs (session codes and titles) Required Slide Speakers, please list the Breakout Sessions, TLC Interactive Theaters and Labs that are related to your session. Required Slide Speakers, please list the Breakout Sessions, TLC Interactive Theaters and Labs that are related to your session.

Track Resources Resource 1 Resource 2 Resource 3 Resource 4 Required Slide Track PMs will supply the content for this slide, which will be inserted during the final scrub. Required Slide Track PMs will supply the content for this slide, which will be inserted during the final scrub.

Complete an evaluation on CommNet and enter to win an Xbox 360 Elite!

Please join us for the Community Drinks this evening In Halls 3 & 4 from 18:15 – 19:30

© 2009 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. Required Slide