Export (0) Print
Expand All
3 out of 5 rated this helpful - Rate this topic

Upgrade a SQL Server Failover Cluster Instance (Setup)

You can upgrade a SQL Server failover cluster to a SQL Server 2012 failover cluster by using the SQL Server Installation Wizard or a command prompt.

During the failover cluster upgrade, downtime is limited to failover time and the time that is required for upgrade scripts to run. If you follow the failover cluster rolling upgrade process, your downtime is minimal. Depending on whether you have all the prerequisites on the failover cluster nodes, you might incur additional downtime while you install these prerequisites. For more information about how to minimize the downtime during upgrade, see the Best Practices Before Upgrading Failover Cluster section on this page.

For more information about how to upgrade, see Supported Version and Edition Upgrades and Upgrade to SQL Server 2012.

For more information about sample syntax for command prompt usage, see Install SQL Server 2012 from the Command Prompt.

Before you begin, review the following important information:

  • Before Installing Failover Clustering

  • Use Upgrade Advisor to Prepare for Upgrades .

  • Upgrade Database Engine

  • Setup installs .NET Framework 4.0 on a clustered operating system. To minimize any possible downtime, consider installing .NET Framework 4.0 before you run Setup.

  • To make sure that the Visual Studio component can be installed correctly, SQL Server requires you to install an update. SQL Server Setup checks for the presence of this update and then requires you to download and install the update before you can continue with the SQL Server installation. To avoid the interruption during SQL Server Setup, you can download and install the update before running SQL Server Setup as described below (or install all the updates for .NET 3.5 SP1 available on Windows Update):

    If you install SQL Server 2012 on a computer with the Windows Vista SP2 or Widows Server 2008 SP2 operating system, you can get the required update from here

    If you install SQL Server 2012 on a computer with the Windows 7 SP1 or Windows 2008 R2 SP1 operating system, this update in included.

  • .NET Framework 3.5 SP1 is no longer installed by SQL Server Setup, but may be required while installing SQL Server on Windows Vista or Windows Server 2008. For more information, see SQL Server 2012 Release Notes.

  • For local installations, you must run SQL Server Setup as an administrator. If you install SQL Server from a remote share, you must use a domain account that has read permissions on the remote share.

  • To upgrade an instance of SQL Server to a SQL Server 2012 failover cluster, the instance being upgraded must be a failover cluster.

    To move a stand-alone instance of SQL Server to a SQL Server 2012 failover cluster, install a new SQL Server 2012 failover cluster, and then migrate user databases from the stand-alone instance by using the Copy Database Wizard. For more information, see Use the Copy Database Wizard.

To upgrade a SQL Server failover cluster to SQL Server 2012, you must run setup with upgrade action on each failover cluster node, one at a time, starting with the passive nodes. As you upgrade each node, it is left out of the possible owners of the failover cluster. If there is an unexpected failover, the upgraded nodes do not participate in the failover until cluster resource group ownership is moved to an upgraded node by SQL Server Setup.

By default, Setup automatically determines when to fail over to an upgraded node. This depends on the total number of nodes in the failover cluster instance and the number of nodes that have already been upgraded. When half of the nodes or more have already been upgraded, Setup causes a failover to an upgraded node when you perform upgrade on the next node. Upon failover to an upgraded node, the cluster group is moved to an upgraded node. All the upgraded nodes are put in the possible owners list and all the nodes that are not yet upgraded are removed from the possible owners list. As you upgrade each remaining node, it is added to the possible owners of the failover cluster.

This process results in downtime limited to one failover time and database upgrade script execution time during the whole failover cluster upgrade.

To control the failover behavior of cluster nodes during the upgrade process, run the upgrade operation at the command prompt and use the /FAILOVERCLUSTERROLLOWNERSHIP parameter. For more information, see Install SQL Server 2012 from the Command Prompt.

Note   If there is a single-node failover cluster, SQL Server Setup takes the SQL Server resource group offline.

If you specified domain groups for the cluster security policy, you cannot specify service SID on Windows Server 2008. If you want to use the service SID, you need to perform a side by side upgrade.

When you select Database Engine for upgrade, full-text search is included in the setup regardless of whether it was installed in SQL Server 2005.

If full-text search was enabled in SQL Server 2005, Setup rebuilds the full-text search catalog regardless of the options available to you.

There are two possible scenarios for upgrades:

  1. SQL Server failover cluster is currently configured on a single subnet: You must first upgrade the existing cluster to SQL Server 2012 by launching Setup and following the upgrade process.After completing the upgrade of the existing failover cluster, add a node that is on a different subnet using the AddNode functionality. Confirm the IP address resource dependency change to OR in the cluster network configuration page. You now have a SQL Server multi-subnet failover cluster.

  2. SQL Server failover cluster is currently configured on multiple subnets using the stretch V-LAN technology: You must first upgrade the existing cluster to SQL Server 2012. Because stretch V-LAN technology configures a single subnet, the network configuration must to be changed to multiple subnets, and change the IP address resource dependency using the Windows Failover Cluster administration tool and change the IP dependency to OR.

Best Practices Before Upgrading a SQL Server Failover Cluster

To eliminate unexpected downtime caused by a restart, preinstall the no-reboot package for .NET Framework 4.0 on all the failover cluster nodes before you run the upgrade on the cluster nodes. We recommend the following steps to preinstall the prerequisites:

  • Install the no-reboot package for .NET Framework 4.0, and upgrade only the shared components starting with the passive nodes. This installs .NET Framework 4.0, Windows Installer 4.5, and SQL Server support files.

  • Restart one or more times, as required.

  • Fail over to an upgraded node.

  • Upgrade the shared components on the last remaining node.

After all the shared components are upgraded and prerequisites are installed, start the failover cluster upgrade process. You have to run upgrade on each failover cluster node, starting with the passive nodes first and making your way toward the node that owns the cluster resource group.

  • You cannot add features to an existing failover cluster.

  • Changing the edition of the failover cluster is limited to certain scenarios. For more information, see Supported Version and Edition Upgrades.

To upgrade a SQL Server failover cluster

  1. Insert the SQL Server installation media, and from the root folder, double-click Setup.exe. To install from a network share, move to the root folder on the share, and then double-click Setup.exe. You may be asked to install the prerequisites, if they are not previously installed.

  2. Important note Important

    For more information about steps 3 and 4, see the Best Practices Before Upgrading Failover Cluster section.

  3. After prerequisites are installed, the Installation Wizard starts the SQL Server Installation Center. To upgrade an existing instance of SQL Server, click Upgrade from SQL Server 2005, SQL Server 2008, or SQL Server 2008 R2.

  4. If Setup support files are required, SQL Server Setup installs them. If you are instructed to restart your computer, restart before you continue.

  5. The System Configuration Checker runs a discovery operation on your computer. To continue, click OK.

  6. On the Product Key page, enter the PID key for the new version edition that matches the edition of the old product version. For example, to upgrade an Enterprise failover cluster, you must supply a PID key for SQL Server Enterprise. Click Next to continue. Be aware that the PID key that you use for a failover cluster upgrade must be consistent across all failover cluster nodes in the same SQL Server instance. For more information, see Editions and Components of SQL Server 2012 and Supported Version and Edition Upgrades.

  7. On the License Terms page, read the license agreement, and then select the check box to accept the license terms and conditions. To help improve SQL Server, you can also enable the feature usage option and send reports to Microsoft. Click Next to continue. To end Setup, click Cancel.

  8. On the Select Instance page, specify the SQL Server instance to upgrade to SQL Server 2012. Click Next to continue.

  9. On the Feature Selection page, the features to upgrade are preselected. A description for each component group appears in the right pane after you select the feature name. Be aware that you cannot change the features to be upgraded, and you cannot add features during the upgrade operation. To add features to an upgraded instance of SQL Server 2012 after the upgrade operation is complete, see Add Features to an Instance of SQL Server 2012 (Setup).

    The prerequisites for the selected features are displayed on the right-hand pane. SQL Server Setup will install the prerequisite that are not already installed during the installation step described later in this procedure.

  10. On the Instance Configuration page, fields are automatically populated from the old instance. You can choose to specify the new InstanceID value.

    Instance ID - By default, the instance name is used as the Instance ID. This is used to identify installation directories and registry keys for your instance of SQL Server. This is the case for default instances and named instances. For a default instance, the instance name and instance ID would be MSSQLSERVER. To use a nondefault instance ID, select the Instance ID check box and provide a value. If you override the default value, you must specify the same Instance ID for the instance being upgraded on all the failover cluster nodes. The Instance ID for the upgraded instance must match across the nodes.

    Detected instances and features - The grid shows instances of SQL Server that are on the computer where Setup is running. Click Next to continue.

  11. The Disk Space Requirements page calculates the required disk space for the features that you specify, and compares requirements to the available disk space on the computer where Setup is running. For more information, see Disk Space Requirements.

  12. On the Full-Text Search Upgrade page, specify the upgrade options for the databases being upgraded. For more information, see Full-Text Search Upgrade Options.

  13. On the Error Reporting page, specify the information that you want to send to Microsoft that will help improve SQL Server. By default, options for error reporting is enabled. For more information, see Error Reporting.

  14. The System Configuration Checker runs one more set of rules to validate your computer configuration with the SQL Server features that you have specified, before the upgrade operation begins.

  15. The Cluster Upgrade Report page displays the list of nodes in the failover cluster instance and the instance version information for SQL Server components on each node. It displays the database script status and replication script status. In addition, it also displays informational messages on what will occur when you click Next. Depending on the number of failover cluster nodes that have already been upgraded and total number of nodes, Setup displays the failover behavior that happens when you click Next. It also warns about potential unnecessary downtime if you have not installed the prerequisites already.

  16. The Ready to Upgrade page displays a tree view of installation options that were specified during Setup. To continue, click Upgrade. SQL Server Setup will first install the required prerequisites for the selected features followed by the feature installation.

  17. During upgrade, the Progress page provides status so that you can monitor the upgrade progress on the current node as Setup continues.

  18. After the upgrade of the current node, the Cluster Upgrade Report page displays an upgrade status information for all the failover cluster nodes, features on each failover cluster node, and their version information. Confirm the version information that is displayed and continue with the upgrade of the remaining nodes. If the failover to upgraded nodes occurred, this is also apparent on the status page. You can also check in the Windows Cluster administrator tool to confirm.

  19. After upgrade, the Complete page provides a link to the summary log file for the installation and other important notes. To complete the SQL Server installation process, click Close.

  20. If you are instructed to restart the computer, do so now. It is important to read the message from the Installation Wizard when you have finished with Setup. For more information about Setup log files, see View and Read SQL Server Setup Log Files.

  21. To complete the upgrade process, repeat steps 1 to 21 on all the other nodes on the SQL Server failover cluster.

To upgrade to a SQL Server multi-subnet failover Cluster (Existing SQL Server cluster is a non multi-subnet cluster).

  1. Follow the steps 1 through 24 described in the To upgrade a SQL Server failover cluster section above to upgrade your cluster to SQL Server 2012.

  2. Add a node on a different subnet using the AddNode Setup action and confirm the IP address resource dependency to OR on the Cluster Network Configuration page. For more information, see Add or Remove Nodes in a SQL Server Failover Cluster (Setup).

To upgrade a multi-subnet cluster currently using Stretch V-Lan.

  1. Follow the steps 1 through 24 described in the To upgrade a SQL Server failover cluster section above to upgrade your cluster to SQL Server 2012.

  2. Change the network settings to move the remote node to a different subnet.

  3. Using the Windows Failover Cluster management tool, add a new IP address for the new subnet set the IP address resource dependency to OR.

After you upgrade to SQL Server 2012, complete the following tasks:

  • Register your servers

    Upgrade removes registry settings for the previous SQL Server instance. After you upgrade, you must reregister your servers.

  • Update statistics

    To help optimize query performance, we recommend that you update statistics on all databases following upgrade. Use the sp_updatestats stored procedure to update statistics in user-defined tables in SQL Server databases.

  • Configure your new SQL Server installation

    To reduce the attackable surface area of a system, SQL Server selectively installs and enables key services and features. For more information about surface area configuration, see the readme file for this release.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.