Explanation/Reference:
Note:
* From scenario:
/The current SQL Server environment consists of a single instance failover cluster of SQL Server 2008 R2 Analysis Services (SSAS). The virtual server name of the cluster is SSASCluster. The cluster includes two nodes: Node1 and Node2. Node1 is currently the active node. In anticipation of the upgrade, the prerequisites and shared components have been upgraded on both nodes of the cluster, and each node was rebooted during a weekly maintenance window.
The upgrade must minimize user intervention and administrative effort. So we'll upgrade using the scripted method rather than the GUI method.
* (box 1)
/SQL Server Setup provides the ability to generate a configuration file based upon the system default and run-time inputs. You can use the configuration file to deploy SQL Server throughout the enterprise with the same configuration. You can also standardize manual installations throughout the enterprise, by creating a batch file that launches Setup.exe.
/How to generate a configuration file
Insert the SQL Server installation media. From the root folder, double-click Setup.exe. To install from a network share, locate the root folder on the share, and then double-click Setup.exe.
Follow the wizard through to the Ready to Install page. The path to the configuration file is specified in the Ready to Install page in the configuration file path section. For more information about how to install SQL Server, see Install SQL Server 2012 from the Installation Wizard (Setup).
Cancel the setup without actually completing the installation, to generate the INI file.
* (box 2) First upgrade the passive node node2.
To be able to use the configuration file we use the command prompt. After the upgrade, the cluster will fail over to the upgraded node.
*( Box 3) upgrade Node1 (which is now the passive node)
.
* You can upgrade a SQL Server failover cluster to a SQL Server 2008 failover cluster by using the SQL Server Installation Wizard or a command prompt. One of the main features of SQL Server 2008 failover clustering is minimal downtime for rolling upgrades and updates.
* 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.
* To upgrade a SQL Server failover cluster to SQL Server 2008 R2, you must run the Setup on one failover cluster node at a time, starting with the passive nodes. Setup determines when to fail over to the upgraded node, depending 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 by default will cause a failover to an upgraded node.
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 to control the failover behavior before the upgrade operation takes the node offline. Use of this parameter is as follows:
/FAILOVERCLUSTERROLLOWNERSHIP=0 will not roll cluster ownership (move group) to upgraded nodes, and does not add this node to the list of possible owners of the SQL Server cluster at the end of upgrade.
/FAILOVERCLUSTERROLLOWNERSHIP=1 will roll cluster ownership (move group) to upgraded nodes, and will add this node to the list of possible owners of the SQL Server cluster at the end of upgrade.
/FAILOVERCLUSTERROLLOWNERSHIP=2 is the default setting. It will be used if this parameter is not specified. This setting indicates that SQL Server Setup will manage cluster ownership (move group) as needed.
Reference: Install SQL Server 2012 Using a Configuration File
Reference: How to: Install SQL Server 2008 R2 from the Command Prompt