Вы находитесь на странице: 1из 9

Installing a SQL 2008 R2 Clustered Instance

Installing a SQL 2008 R2 Clustered Instance

Table of Contents
Installing a SQL 2008 R2 Clustered Instance ........................................................................... 1
Exercise 1 Install a Single Node SQL Server 2008 R2 Clustered Instance ......................................................................2 Exercise 2 Add a Node to an Existing SQL Server 2008 R2 Failover Cluster Using Command Line ................................5 Exercise 3 Perform Post-Installation Tasks ....................................................................................................................6

Installing a SQL 2008 R2 Clustered Instance

Installing a SQL 2008 R2 Clustered Instance


Objectives
After completing this lab, you will be better able to: Install a single node SQL Server 2008 R2 clustered instance Add a Node to an existing SQL Server 2008 R2 Failover Cluster using command line Perform Post-Installation Tasks

Scenario

During this lab, you will create a highly available SQL Server 2008 R2 clustered instance on a Windows Server 2008 R2 Failover Cluster using Slipstreaming process. 90 Minutes

Estimated Time to Complete This Lab Computers used in this Lab

W2K8R2DC

W2K8R2N1

W2K8R2N2

The password for the Administrator account on all computers in this lab is: Password1

Page 1 of 7

Installing a SQL 2008 R2 Clustered Instance

Exercise 1 Install a Single Node SQL Server 2008 R2 Clustered Instance


Scenario
You are a SQL Server DBA and have been directed to install a single node SQL Server 2008 R2 clustered instance on a Windows Server 2008 R2 failover cluster node W2K8R2N1. Tasks Complete the following task on: W2K8R2N1 1. Install a single node SQL Server 2008 R2 clustered instance on W2K8R2N1 Detailed Steps
a. Run SQL Server 2008 R2 setup from C:\ SQL2008R2_Setup_Binaries\setup.exe b. On the left side of SQL Server Installation Center select Installation. c. On the right side of SQL Server Installation Center, click New SQL Server failover

cluster installation.
d. Verify there are no errors on the Setup Support Rules page and click OK.

Note: Click Show details button to see all the setup support rules that were run. Click View detailed report to see more details
e. On the Setup Support Files page, click Install. f.

Verify there are no errors on the Setup Support Rules page and click Next. product key if it is not already entered. Click Next.

g. On the Product Key page, verify that Enter the product key is selected. Type the h. On the next page review and accept the License Terms and click Next. i.

On the Feature Selection page select the following features and click Next: Database Engine Services (SQL Server Replication and Full-Text search will be automatically checked) Client Tools Connectivity Integration Services Client tools Backwards compatibility SQL Server Books Online Management Tools Basic (Management Tools Complete will be automatically checked)

j.

On the Instance Configuration page type the SQL Server Network name,SQL2008R2VS. Choose if it will be the default instance (MSSQLSERVER) or a named instance if you already have a default one. For this lab, we will install a named instance. Click the radio button next to Named Instance and type the Named Instance name, INST1. The Instance ID input box will be automatically completed with the same value of instance name. Click Next. The next page is the Cluster Resource Group where you can choose the cluster group name for SQL Server 2008 R2. Leave the default.. Click Next.

k. On the Disk Space Requirements screen, review the information and click Next. l.

m. The Cluster Disk Selection page will show the available disks (Green). Check the

box for the disk labeled SQL2008R2Base. Click Next. Note: On the Cluster Disk Selection page, you cannot select the mounted drives. Only base drives can be selected. Later on, the setup wizard allows you to use the mounted

Page 2 of 7

Installing a SQL 2008 R2 Clustered Instance Tasks Detailed Steps drives if you had selected the base drive in this page
n. On the Cluster Network Configuration page, uncheck DHCP and type the SQL

Server IP address (type 192.168.1.6) for the Public Network. Click Next.
o. In the Cluster Security Policy page, verify that Use service SIDs (recommended) is

selected. Click Next.


p. In the Server Configuration page, on the Service Accounts tab Use

SQL2K8WKS\SQL2K8R2SVC for SQL Server Database Engine service account and SQL2K8WKS\SQLAgent2K8R2SVC for SQL Agent service account. Password for both these accounts is Password1. Click Next.
q. The Database Engine Configuration screen will allow to configure following:

Account Provisioning (Authentication and Administration rights) Data Directories (Location for Data, Logs, tempdb, backups) FILESTREAM (Enable Filestream for T-SQL)

Click Account Provisioning tab.. Click on Add Current User button to add the SQL2K8WKS\cluadmin user as a SQL Server administrator. This step is necessary because SQL Server 2008 R2 does not configure the Windows Builtin\Administrators group as SQL Server system administrators. Click the Data Directories tab. By default, the setup will just use one disk for everything even if you have selected more disks. Select the proper disks for data, log, tempdb and backup. For this exercise, use the following: Data root directory: F:\SQL2008System System database directory: F:\SQL2008System\MSSQL10.<InstanceID>\MSSQL\Data User database directory: F:\SQL2008Data1\Data User databaselog directory: F:\SQL2008Log\Log Temp DB directory: F:\SQL2008Tempdb\Tempdb Temp DB log directory: F:\SQL2008Tempdb\Tempdb Backup directory: F:\SQL2008Backup\Backup

Note: Notice that we are using mount points for user database, log, tempdb and backup. Ensure that you do not use the root of the mount point (for example F:\SQL2008Data), because you cannot assign NTFS file system permissions to it. That is why we are creating a folder on the root directory (for example F:\SQL2008Data\Data) and using that folder for the SQL Server databases. Failure to create the folder on the root directory may result in a failed SQL Server installation.
r. Click Next. s. Leave unchecked the option in the Error Reporting page and click Next. t. The Cluster Installation Rules checks will run. Verify there are no errors and click

Next. Note: Click Show details button to see all the setup support rules that were run. Click View detailed report to see more details. Notice there is a rule called Update Setup Media Language Compatibility. This rule indicates a slipstream setup. Click the Passed link next to this rule for more details
u. On the Ready to Install page, verify that the information is correct and click

Install. Note: On the Ready to Install page, notice the path to the configuration file is specified. The setup infrastructure writes out all the appropriate parameters in the configuration file for the actions that were run, with the exception of sensitive

Page 3 of 7

Installing a SQL 2008 R2 Clustered Instance Tasks Detailed Steps information like passwords. If you want to stop the installation at this time, you can click Cancel. Later when you are ready you can run the installation through the command prompt and supply the ConfigurationFile.ini using the ConfigurationFile parameter. Example of running setup.exe using the configuration file: setup.exe /ConfigurationFile=ConfigurationFile.INI For additional information refer to Books Online topic How to: Install SQL Server 2008 R2 Using a Configuration File.
v. Wait for the installation to complete and then click Close.

Note: By default, the SQL Server 2008 R2 setup files are located on the cluster node in the %Program Files%\Microsoft SQL Server\100\Setup Bootstrap\Log\<datetime> directory

Page 4 of 7

Installing a SQL 2008 R2 Clustered Instance

Exercise 2 Add a Node to an Existing SQL Server 2008 R2 Failover Cluster Using Command Line
Scenario
You are a SQL Server DBA and have been directed to add a node (W2K8R2N2) to the SQL Server 2008 R2 clustered instance on W2K8R2N1. In the previous exercise, we ran setup using the GUI. In this exercise, we will run setup using command line. Tasks Complete the following task on: W2K8R2N2 1. Open the Command Prompt Detailed Steps
a. On W2K8R2N2 cluster node, open a command prompt with elevated privileges

(Start All Programs Accessories Right click Command Prompt and select Run as administrator).
b. Run setup from command prompt to add node using the merged drop that was

created in previous exercise slipstream steps. Replace <INSTANCE_NAME> parameter with the instance name of your existing SQL Server 2008 R2 clustered instance. For example, if your SQL Server 2008 R2 server name is SQL2008R2VS\INST1, the instance name is INST1. For default instance, use MSSQLServer for the instance name.
C:\> \\W2K8R2N1\C$\SQL2008R2_Setup_Binaries\setup.exe /q /ACTION=AddNode /INSTANCENAME="<INSTANCE_NAME>" /SQLSVCACCOUNT="SQL2K8WKS\SQL2K8R2SVC" /SQLSVCPASSWORD="Password1" /AGTSVCACCOUNT="SQL2K8WKS\SQLAgent2K8R2SVC" /AGTSVCPASSWORD="Password1" / IACCEPTSQLSERVERLICENSETERMS /INDICATEPROGRESS

Note: SQL Server 2008 R2 introduced the parameter IACCEPTSQLSERVERLICENSETERMS. This parameter is not optional and is required for unattended installation. So if you've got existing SQL Server 2008 RTM scripts for installation and you want to use them with SQL Server 2008 R2, make sure you update them accordingly. The setup will run the add node action with the parameters specified in the command line. We will be able to see the progress on the command line as we have added the optional INDICATEPROGRESS parameter. It is a good idea to have this parameter at least for the first time.

Page 5 of 7

Installing a SQL 2008 R2 Clustered Instance

Exercise 3 Perform Post-Installation Tasks


Scenario
You are a SQL Server DBA and have installed a SQL Server 2008 R2 clustered instance on two node Windows Server 2008 R2 failover cluster. After installing SQL Server, you must perform some basic post-installation tasks. Tasks Complete the following task on: W2K8R2N1 1. Review all the setup logs
a. Click the Start button in the lower left hand corner of the display. b. Highlight Administrative Tools and select Failover Cluster Manager. c. The snap-in opens on the desktop.

Detailed Steps
a. By default, the SQL Server 2008 R2 setup files are located on the cluster node in

the %Program Files%\Microsoft SQL Server\100\Setup Bootstrap\Log\<datetime> directory.


b. Review the summary.txt file.

Complete the following task on: W2K8R2N1 2. Open the Failover Cluster Manager snap-in on W2K8R2N1

Complete the following task on: W2K8R2N1 3. Review the SQL Server 2008 R2 resources and dependencies

a. In the left pane, click the Windows cluster name and then click Services and

Applications.
b. Click the newly created SQL Server 2008 R2 service group. c. Verify that all the SQL Server resources are created. Review the properties of all

the resources. Verify that both the cluster nodes are listed as possible owners in the Advanced Policies tab and the dependencies are listed properly in the Dependencies tab.
d. If you are using mount points, verify that the mount points are dependent on the

base drive and SQL Server resource is dependent on the mount points. By default, SQL Server resource is only dependent on the base drive. Create the other dependencies manually.
e. In the right hand pane of Failover Cluster Manager snap-in, in the Action section,

click Show Dependency Report to view the dependency report. Verify that the dependencies are correct. Complete the following task on: W2K8R2N1 4. Review the SQL Server resource failure policy
a. Right click the SQL Server resource and select Properties. b. Select the Policies tab and review the settings.

Page 6 of 7

Installing a SQL 2008 R2 Clustered Instance Tasks Complete the following task on: W2K8R2N1 5. Set the Preferred Node Order for Failover
a. Open a command prompt on W2K8R2N1. b. Ping the SQL Server 2008 R2 IP address (192.168.1.6) and ensure you get a reply

Detailed Steps
a. Right click the SQL Server 2008 R2 service group and select Properties. b. On the General tab, select the preferred owners order.

Complete the following task on: W2K8R2N1 6. Verify SQL Server connectivity and name resolution

back. Also ping using the a parameter to verify that the address is resolved to SQL Server network name. Example
ping 192.168.1.6 ping a 192.168.1.6 c. Ping the SQL Server network name and ensure you get a reply back. d. Repeat above steps on W2K8R2N2. e. In real world, repeat above steps from a client machine too. a. In Failover Cluster Manager in the left-hand pane under Services and

Complete the following task on: W2K8R2N1 7. Test failover of the SQL Server 2008 R2 service group

Applications, right-click on the SQL Server 2008 R2 service group.


b. Select Move this service or application to another node and choose another

node in the cluster.


c. Complete the confirmation pop-up. d. Observe the service fails over and comes online on another node.

Complete the following task on: W2K8R2N1 8. Verify the SQL Server cluster configuration using SQL Server Management Studio

a. Open SQL Server Management Studio (Start All Programs Microsoft SQL

Server 2008 R2 SQL Server Management Studio).


b. Connect to the SQL Server 2008 R2 clustered instance. By default, the server

name is populated in the Connect to Server window. Review the information and Click Connect.
c. Open a New Query window and type the following commands to verify the disk

and node configuration respectively.


SELECT * FROM sys.dm_io_cluster_shared_drives; SELECT * FROM sys.dm_os_cluster_nodes; d. Type the following commands to review the SQL Server edition and version SELECT @@VERSION; SELECT SERVERPROPERTY('ProductVersion') AS ProductVersion, SERVERPROPERTY('ProductLevel') AS ProductLevel, SERVERPROPERTY('Edition') AS Edition; e. Alternately, you can click Tools from the left pane in SQL Server Installation

Center and click Installed SQL Server features discovery report. This will show you a report of all the SQL Server products and features that are installed in the local server.

Page 7 of 7

Вам также может понравиться