Installing a Two-node SQL Server 2008 Cluster - Advanced option
November 12, 2008
In Part II of this series, we showed you a step-by-step example of Integrated installation of SQL Server 2008 cluster. In this article, we will move onto the other installation option Advanced/Enterprise installation. This option consists of two steps. The Prepare step prepares all nodes of the failover cluster, and installs SQL Server binaries on each node. Nodes in the cluster are configured during this step. After you prepare the nodes, you only need to run the Complete step on the active node that owns the shared disks. This step completes the failover cluster instance and makes it operational.
This article series is written based on the SQL Server 2008 RTM Developer Edition.
The steps are shown in detail below.
1. Prepare both nodes of the failover cluster, NODE1 and NODE2, to be operational.
Our SQL Server installation media is in a shared folder called sqlserver2008 on a remote computer demopc. Here is the command we run in the command prompt on each node.
\\demopc\sqlserver2008\Setup.exe /q /ACTION=PrepareFailoverCluster /FEATURES=SQL /INSTANCENAME= "MSSQLSERVER" /INSTANCEDIR="C:\Program Files\Microsoft SQL Server" /INSTALLSHAREDDIR="C:\Program Files\Microsoft SQL Server" /SQLSVCACCOUNT="PowerDomain\SqlService" /SQLSVCPASSWORD="P@ssw0rd" /AGTSVCACCOUNT="PowerDomain\SqlService" /AGTSVCPASSWORD="P@ssw0rd" /SQLDOMAINGROUP="PowerDomain\SQLAdmins" /AGTDOMAINGROUP="PowerDomain\SQLAdmins"
Download this code.
Figure 1 shows the output from the command.
Click for larger image
Each parameter in the command is explained in the table below.
After the installation of each node, we need to check the installation log files under the SQL Server binary directory. Figure 2 shows the list of log files on NODE1.
You can start with the summary file, Summary_node1_xxxxxx.txt. This file provides the result of each component installation, and gives you a hint as to which component had the problem if the installation failed.
Notice that the binaries have been installed under C:\Program Files\Microsoft SQL Server. However, database files have not been created on the shared disks D: and L:.
2. The Complete step runs only on the active node. In our case, NODE1 owns the shared disk. Run the following command on NODE1.
\\demopc\sqlserver2008\setup.exe /q /ACTION=CompleteFailoverCluster /INSTANCENAME="MSSQLSERVER" /FAILOVERCLUSTERNETWORKNAME="SQL2008Cluster" /FAILOVERCLUSTERGROUP="SQL Server 2008 Group" /FAILOVERCLUSTERDISKS="SQL Data" "SQL Log" /FAILOVERCLUSTERIPADDRESSES="IPv4;192.168.1.12;Public;255.255.255.0" /SQLCOLLATION="SQL_Latin1_General_CP1_CS_AS" /SQLSYSADMINACCOUNTS="PowerDomain\SqlService" /INSTALLSQLDATADIR="D:\SQLServer" /SQLUSERDBLOGDIR="L:\SQLServer\MSSQL10.MSSQLSERVER\MSSQL\Log" /SQLTEMPDBLOGDIR="L:\SQLServer\MSSQL10.MSSQLSERVER\MSSQL\Log"
Download this code.
Notice that the value for the ACTION parameter is CompleteFailoverCluster. Figure 4 shows the output from the command.
Each parameter is explained in the table below.
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 see database files on the shared disks D: and L:.
We can also perform a failover test to ensure automatic failover in case of a hardware or software failure. As shown in Figure 6, 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 7 shows the SQL Server cluster after the failover. Our cluster installation is complete.
In this series, we have illustrated how to install a SQL Server 2008 cluster from the command prompt using both the Integrated and Advanced installation options.