Setting up a Two-NODE SQL Server 2008 Cluster from the Command Prompt - Integrated Installation
October 8, 2008
In Part 1 of this series, we discussed how to prepare for SQL Server cluster installation on a two-node Windows Server 2003 cluster. We had two machines, NODE1 and NODE2, in our example. In this installment, I will show you how to install SQL Server Database Engine on the cluster. Although Analysis Services can be clustered as well, and even put in the same resource group, it is recommended to install it in a separate group so SQL Server and Analysis Services do not affect each other in the event of a problem. Therefore, we will only install SQL Server Database Engine in the example below. This article series is written based on the SQL Server 2008 RTM Developer Edition.
In the Integrated installation, we create a single-node SQL Server failover cluster instance first. Then we run Setup on each node we want to add to the cluster, and add the node using the Add Node functionality in Setup. These two steps are shown in detail below.
1. Install a single-node SQL Server failover cluster instance on NODE1.
Our SQL Server installation media is in a shared folder called sqlserver2008 on a remote computer demopc. We run the following command in the command prompt (please replace xxxxxxxxx with your own password before you run the command in your environment).
\\demopc\sqlserver2008\setup.exe /q /ACTION=InstallFailoverCluster /FEATURES=SQL /INSTANCENAME="MSSQLSERVER" /INSTANCEDIR="C:\Program Files\Microsoft SQL Server" /INSTALLSHAREDDIR="C:\Program Files\Microsoft SQL Server" /SQLSVCACCOUNT="PowerDomain\SqlService" /SQLSVCPASSWORD="xxxxxxxxx" /AGTSVCACCOUNT="PowerDomain\SqlService" /AGTSVCPASSWORD="xxxxxxxxx" /SQLDOMAINGROUP="PowerDomain\SQLAdmins" /AGTDOMAINGROUP="PowerDomain\SQLAdmins" /SQLCOLLATION="SQL_Latin1_General_CP1_CI_AS" /FAILOVERCLUSTERGROUP="SQL Server 2008 Group" /FAILOVERCLUSTERDISKS="SQL Data" "SQL Log" /FAILOVERCLUSTERIPADDRESSES="IPv4;192.168.1.12;Public;255.255.255.0" /FAILOVERCLUSTERNETWORKNAME="SQL2008Cluster" /SQLSYSADMINACCOUNTS="PowerDomain\SqlService" /SQLUSERDBLOGDIR="L:\MSSQL10.MSSQLSERVER\MSSQL\Log" /SQLTEMPDBLOGDIR="L:\MSSQL10.MSSQLSERVER\MSSQL\Log" /INSTALLSQLDATADIR="D:\MSSQL10.MSSQLSERVER\MSSQLSERVER"
Download this code.
Figure 1 shows the output from the command. The passwords are masked in the figure.
As you can see in Figure 1, a few parameters are passed to setup.exe to configure the new failover cluster instance. Each parameter is explained in the table below.
If you encounter a broken fusion ATL error during rule checks, you can install the SQL Server Setup support files from the installation media before Setup. To do so, manually execute SqlSupport.msi under the setup folder in the installation media. For more information, please refer to http://support.microsoft.com/kb/955792.
After the installation, we need to check the log files under the SQL Server program directory. Figure 2 shows the list of log files.
The summary file, in our case, Summary_NODE1_20080824_221906.txt provides the final results of each component installation.
If the installation succeeded, the SQL Server cluster group should look as in Figure 3. Please note that only NODE1 is included in the cluster so far.
2. Add NODE2 to the cluster using the Add NODE functionality in Setup. Run the following command in the command prompt.
\\demopc\sqlserver2008\setup.exe /q /ACTION=AddNode /INSTANCENAME="MSSQLSERVER" /SQLSVCACCOUNT="PowerDomain\SqlService" /SQLSVCPASSWORD="xxxxxxxxx" /AGTSVCACCOUNT="PowerDomain\SqlService" /AGTSVCPASSWORD="xxxxxxxxxx"
Download this code.
Notice that the value for the ACTION parameter is AddNode, which specifies adding a new node into the cluster. Figure 4 shows the output from the command. The passwords are masked in the figure.
After the installation, we need to verify the result of the installation by checking the log files under C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log. If the installation was successful, we can perform a failover test to ensure automatic failover in case of a hardware or software failure. As shown in Figure 5, right click the SQL Server 2008 Group in Cluster Administrator, and choose Move Group.
The SQL Server cluster group should fail over to NODE2, and the new SQL Server failover cluster instance should start running on NODE2. Figure 6 shows the SQL Server cluster after the failover.
In Part 2 of this series, we have illustrated how to install a SQL Server 2008 cluster using the Integrated Installation option. In the next installment, we will explore the Advanced Installation option.