Skip to content

upgrade-a-sql-server-failover-cluster-instance-setup.md

Latest commit

 

History

History
108 lines (66 loc) · 11.2 KB

upgrade-a-sql-server-failover-cluster-instance-setup.md

File metadata and controls

108 lines (66 loc) · 11.2 KB
title Upgrade a SQL Server Failover Cluster Instance (Setup) | Microsoft Docs
ms.custom
ms.date 01/22/2016
ms.prod sql
ms.reviewer
ms.technology high-availability
ms.topic conceptual
helpviewer_keywords
upgrading clusters
clusters [SQL Server], upgrading
failover clustering [SQL Server], creating clusters
clusters [SQL Server], creating
failover clustering [SQL Server], upgrading
ms.assetid ea8b7d66-e5a1-402f-9928-8f7310e84f5c
author MashaMSFT
ms.author mathoma
manager craigg

Upgrade a SQL Server Failover Cluster Instance (Setup)

[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md] You can upgrade a [!INCLUDEssNoVersion] failover cluster to a [!INCLUDEssCurrent] failover cluster by using the [!INCLUDEssNoVersion] setup UI or from a command prompt.

For local installations, you must run [!INCLUDEssNoVersion] Setup as an administrator. If you install [!INCLUDEssNoVersion] from a remote share, you must use a domain account that has read permissions on the remote share.

Before upgrading, see Upgrade a SQL Server Failover Cluster Instance.

To Upgrade a [!INCLUDEssNoVersion] Failover Cluster

To upgrade a [!INCLUDEssNoVersion] failover cluster

  1. From the [!INCLUDEssNoVersion] installation media for the edition that matches the edition you are upgrading, double-click setup.exe in the root folder. You may be asked to install the prerequisites, if they are not previously installed.

  2. After prerequisites are installed, the Installation Wizard starts the [!INCLUDEssNoVersion] Installation Center. To upgrade an existing instance of [!INCLUDEssNoVersion], select your instance.

  3. If [!INCLUDEssNoVersion] setup support files are required, [!INCLUDEssNoVersion] setup installs them. If you are instructed to restart your computer, restart before you continue.

  4. The System Configuration Checker runs a discovery operation on your computer. To continue, [!INCLUDEclickOK].

  5. 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 [!INCLUDEssEnterprise]. 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 [!INCLUDEssNoVersion] instance.

  6. 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 [!INCLUDEssNoVersion], you can also enable the feature usage option and send reports to [!INCLUDEmsCoName]. Click Next to continue. To end Setup, click Cancel.

  7. On the Select Instance page, specify the [!INCLUDEssNoVersion] instance to upgrade to [!INCLUDEssCurrent]. Click Next to continue.

  8. 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 [!INCLUDEssSQL14] after the upgrade operation is complete, see Add Features to an Instance of SQL Server 2016 (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. To save time, you should pre-install these prerequisites on each node.

  9. 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 [!INCLUDEssNoVersion]. 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 [!INCLUDEssNoVersion] that are on the computer where setup is running. Click Next to continue.

  10. 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.

  11. 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.

  12. On the Error Reporting page, specify the information that you want to send to [!INCLUDEmsCoName] that will help improve [!INCLUDEssNoVersion]. By default, options for error reporting is enabled.

  13. The System Configuration Checker runs one more set of rules to validate your computer configuration with the [!INCLUDEssNoVersion] features that you have specified, before the upgrade operation begins.

  14. The Cluster Upgrade Report page displays the list of nodes in the failover cluster instance and the instance version information for [!INCLUDEssNoVersion] 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.

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

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

  17. 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.

  18. After upgrade, the Complete page provides a link to the summary log file for the installation and other important notes. To complete the [!INCLUDEssNoVersion] installation process, click Close.

  19. 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.

  20. To complete the upgrade process, repeat these steps on all the other nodes on the [!INCLUDEssNoVersion] failover cluster.

To upgrade a [!INCLUDEssNoVersion] Multi-Subnet Failover Cluster

To upgrade to a [!INCLUDEssNoVersion] multi-subnet failover Cluster (Existing [!INCLUDEssNoVersion] cluster is a non multi-subnet cluster).

  1. Follow the steps above to upgrade your cluster to [!INCLUDEssCurrent].

  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 above to upgrade your cluster to [!INCLUDEssCurrent].

  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.

Next Steps

After you upgrade to [!INCLUDEssCurrent], complete the following tasks:

See Also

Upgrade a SQL Server Failover Cluster Instance
View and Read SQL Server Setup Log Files
Add Features to an Instance of SQL Server 2016 (Setup)