In the example shown in Figure 6.12 an existing Resource Group was selected.. This Resource Group was created before the SQL Server 2008 installer was launched and this Resource Group ha
Trang 1In the example shown in Figure 6.12 an existing Resource Group was selected
This Resource Group was created before the SQL Server 2008 installer was
launched and this Resource Group has the disks already located in it
New & Noteworthy…
Creating Clustered
Resource Group During Installation
The ability to create the cluster resource group and select the disks for the
Resource Group during the SQL Server 2008 installation is a new feature
In prior versions of Microsoft SQL Server you had to manually create the
Resource Group and move the hard drives into the resource group This
addition of this feature into the SQL Server installer is a huge plus for
SQL Server.
By placing this functionality directly into the SQL Server installer as
DBAs we now need to rely less on the system administrators who
assemble the servers and cluster the Windows operating system to set up
the resource groups and hard drives We can now, without having any
additional knowledge of the Windows Cluster Administrator tool, set up
the SQL Server quickly and easily in a Windows Cluster.
Trang 2On the next screen select the disks that you wish to use for the SQL Server You should select any and all hard drives that you will be using for the SQL Server Additional hard drives can be added later through the Cluster Manager As you can see in Figure 6.13 only disks that do not have other resources dependent on them are available for use by the SQL Server In this case the Q drive is in use as the quorum and by the MSDTC service The Q drive can be used by both of these because both of them are in the same Resource Group
Exam Warning
Microsoft loves to test on new technology and features The fact that this is new means that it is more likely to be on the exam.
Figure 6.12 Cluster Resource Group Screen
Trang 3On the next screen you select the IP addresses you will be using for the clustered SQL Server instance You can select each network that is set up on the cluster
and configure a separate IP address for each network In the example shown in
Figure 6.14 there are two networks shown One is the public network, which is
the network that the client computers will connect to the instance The other
is the private network, which is the network that the nodes in the cluster use
to talk to each other The names that are shown are the names of the network
connections in the network control panel
Figure 6.13 Cluster Disk Selection
Trang 4The final cluster page is the Cluster Security Policy screen This screen will be different depending on the operating system installed, and the domain functional level of your Windows domain If you are installing SQL Server 2008 on a
Windows 2008 operating system and the domain functional level is above Windows
2000 mixed, then you will see the screen as shown in Figure 6.15 If you are install-ing on a Windows 2003 operatinstall-ing system or a Windows 2008 operatinstall-ing system and your domain functional level is Windows 2000 mixed mode or lower, then the radio buttons will not be displayed as your only option will be to use the domain groups If you are using Windows 2008 to host your cluster you have the option of using DHCP for your SQL Server If this option is available to you, a check box will be shown in the grid which allows for DHCP If the installer determines that DHCP is not an option for you, then it will not show you the check box
The options allow you to select how you will control which accounts are able to run the SQL Services It is recommended to use the new service SIDs functionally, but the legacy option of using domain groups is still available as an option
Figure 6.14 Cluster Network Configuration
Trang 5If you are using the domain groups option and you have just created the
domain groups shortly before running the SQL Server installer, you may receive an
error saying that the domain group or groups do not exist when they do This is
normal as the domain group simply has not replicated to all the domain controllers
in the domain An example of this error is shown in Figure 6.16 Depending on
how your domain is configured it could take from a few minutes to over an hour
for the domain groups to replicate to all your domain controllers
Figure 6.15 Cluster Security Policy
Figure 6.16 Cluster Security Policy Error Message