Documents
Resources
Learning Center
Upload
Plans & pricing Sign in
Sign Out

Inside SQL Server and Cluster Setup and Troubleshooting.docx

VIEWS: 6 PAGES: 9

									Inside SQL Server Cluster Setup and Troubleshooting Techniques - Part I




The SQL Server Setup process is really straight-forward. An veteran user who has got a little information in setting up
other applications can furthermore go a SQL Cluster Setup but could you repeat that? If issues occur? What will you sort
out if you don’t think it over the newly added disks in the SQL Cluster Setup wizard? What will you sort out if you don’t
think it over the catalog of unfilled nodes in the SQL Cluster Setup screen? What if SQL Cluster Setup wizard fails to
configure other nodes in the cluster?



The foremost objective of this article is to explain the domestic process behind the SQL Server Cluster Setup. Please
annotation this article single explains the SQL Cluster Setup process. It doesn’t explain the SQL Server Standard Setup
process. By conception this article you can explain the means SQL Setup uses to discover the catalog of nodes, catalog of
disks and catalog of interfaces unfilled in the cluster and furthermore the SQL Cluster Setup DLL (SQLCluster.DLL) which
is reliable to sort out the early pre-work pro SQL Setup wizard. This article furthermore explains the how SQL Cluster
Setup detects with the intention of it is vacant to run in a cluster background.



The following run of this article will explain all the registry entries and SQL modules/files which are valuable pro a
thriving failover and how you can mess about with these registry entries and records to troubleshoot the SQL Cluster.
Most of the article talks in this area the SQL Server 2000 but the process and troubleshooting techniques are the same
pro SQL Server 2005. This article will furthermore explain how SQL Cluster Setup configures other nodes to be cluster-
aware.



The failover clustering is used by the SQL Server since SQL Servers are state-full applications. When the SQL Server setup
wizard realizes with the intention of it is vacant to run in a cluster background, the setup wizard will produce you an
option to create SQL Virtual Server. You will excellent this option to create a SQL Cluster. After you excellent the Virtual
Sever option, the setup proceeds to invoke the SQL Cluster modules and go many tasks in the background. These tasks
and process will be explained in point shortly in this article.



The following topics will be covered in this article:

•       How does SQL Setup process detect with the intention of it is vacant to run in a cluster background?

•       How SQL Setup knows which records to imitation?

•        Which SQL module is reliable pro SQL Cluster Setup and could you repeat that? All basic functions it rigging pro a
thriving installation?

•       From everywhere does SQL Setup make a catalog of disks, nodes and interfaces unfilled in the cluster?
•

Inside the then run of the article:

•       SQL Server Cluster Setup Troubleshooting Techniques

•       How does SQL Server cluster setup configure a following node to be cluster-aware?

•       What all registry entries are produced all through the setup and their substance in SQL Cluster and stand-alone?

•       What all SQL “Cluster” modules are hackneyed all through the setup and their substance in a SQL Cluster?

•       How sort out registry entries mess about an valuable role in failover process?

•       What all SQL modules are loaded as a SQL Server Instance is running as Active Node?

•       A practice to manually uninstall SQL Server Instance from a cluster (without running SQL Server Setup wizard)

•       What has been altered in SQL Server 2005 setup process pro cluster?
FIGURE 1.1 – SQL Cluster Server Setup process and Registry Entries.



How does SQL Cluster Setup process detect with the intention of it is vacant to run in a cluster background?

When you start the SQL Server Setup wizard, it will produce you the three options to install the SQL Server Database
engine. The three options are:

•       Local Computer,

•       Remote Computer and

•       Virtual Server



•

The continue option is to install the SQL Server Database engine in a cluster. The setup checks to think it over if it is
vacant to install the SQL Database occasion in a cluster background. The Setup doesn’t really look pro cluster modules or
DLL records. Instead it checks the Cluster Service status. If Cluster Service is running it will produce the option to install
the SQL Virtual Server Instance. You will not think it over Virtual Server option if Cluster Service is not running or
stopped pro one wits. If you’re troubleshooting a SQL Server cluster installation, get on to guaranteed the cluster is up
and running (e.G. Cluster Service is running). Please annotation the Setup Wizard doesn’t check the registry of the
Cluster Service by HKLM\System\CurrentControlSet\Services\ClusSvc. Instead it checks the ClusSvc.Exe logic occasion
which is running in Task Manager and executes a run of API calls via Service Control Manager (SCM) to check the status
of the Cluster service.

How SQL Setup knows which records to imitation

After SQL Server Cluster Setup wizard detects with the intention of it is vacant to install the SQL Server occasion in an
existing cluster, it invokes the SQLCluster.Dll from its BINN directory to carry out the following functions:
DoSQLClusterSetUpWork - Installs the SQL occasion in the cluster

DoUnClusterSetup - Uninstalls the SQL occasion from the cluster

CheckDatabasesForInstance - Checks existing SQL Instances already installed



These functions are explained shortly in this article.



SQL Setup copies records all through the setup process. Setup doesn’t really know which records to imitation. It reads a
gather in a line on the compact disk named 70cluster.Lst. This gather in a line resides by x:\x86\setup directory on the
SQL Server Setup compact disk. You can se all records hackneyed all through the setup by opening the gather in a line in
notepad as publicized in not more than map 1.2:




FIGURE 1.2 – SQL Setup Files hackneyed all through installation



These records are hackneyed to %INSTPATH%. %INSTPATH% is a logic wavering. The complete path in this wavering is
the regard which is entered all through the installation process. The user running the SQL Setup equipment the
complete path. If you always run into one problems with the imitation, get on to guaranteed the 70cluster.Lst gather in
a line contains the entries pro SQL Modules. The preeminent way is to imitation this gather in a line from the SQL
Installation media to the source folder from which you are running the SQL Server setup.



There are other records which are hackneyed by the SQL Server setup wizard. These records are not part of the
70cluster.Lst.
Which SQL module is reliable pro SQL Cluster Setup and could you repeat that? All basic functions it rigging pro a
thriving installation?

Equally explained earlier, SQL Server setup invokes the SQLCluster.Dll module from its BINN directory as it realizes with
the intention of it is vacant to install the SQL Instances in a cluster background.



It executes the following functions from SQLCluster.Dll module:



DoSQLClusterSetUpWork

Equally publicized in Figure 1.1, this function is defined in the SQLCluster.Dll module. The foremost function of this
function is to install the extra SQL Instances in the cluster. This is the foremost step pro installation. The setup performs
the pre-tasks pro the SQL installation by using this function. For model, draw together the catalog of nodes, catalog of
disks, catalog of arrangement interfaces and that. If you add one extra disks to the cluster while the SQL Server setup is
running, the CD-ROM will not be recognizable by the SQL setup process except you exit the setup and start it again from
scrape. This is since the DoSQLClusterSetUpWork function executed from SQLCluster.Dll gathers the cluster
configuration in rank previous to it comes to excellent the disks or nodes unfilled in the SQL Setup.



DoUnClusterSetup

The then function is DoUnClusterSetup. The foremost dependability of this function is to arrange the setup to uninstall
one existing SQL instances from the cluster. You uninstall existing SQL instances from the cluster with the help of this
function. If this function is not implemented at that time you will by no means be agreed an option to uninstall existing
SQL instances.



CheckDatabasesForInstance

The continue function of SQLCluster.Dll is CheckDatabasesForInstance. The foremost function of this function is to check
one existing instances in the cluster. This function is helpful in both the suitcases (when installing an occasion and as
uninstalling an instance). Before SQL Server setup installs or uninstalls one occasion from the cluster, it executes to
check to think it over if the agreed occasion first name is already installed on the logic. SQL Server setup process will not
allow you to install the same occasion if it is already installed. This is how SQL cluster detects the existing installed SQL
instances.



After the SQL Server setup process has finished with this, the then step is to detect the catalog of nodes, catalog of disks
and catalog of interfaces unfilled in the cluster. This bring about is made by the DoSQLClusterSetUpWork. The then
section explains this in point.
From everywhere does SQL Setup make a catalog of disks, nodes and interfaces unfilled in the cluster?

After you be inflicted with selected the “Virtual Server” option, the wizard will draw together the vital in rank from the
cluster. The in rank could include the List of Disks, List of Nodes unfilled in the cluster, catalog of Interfaces and that. This
in rank is vital pro proper installation of the SQL Database instances in the cluster.



The SQL Server Setup wizard completely depends on the Cluster Configuration Database. The SQL Setup retrieves the
cluster configuration in rank from HKLM\Cluster hive. This hive is mapped with %SystemRoot%\Cluster\CLUSDB gather
in a line. The Setup doesn’t really be inflicted with information of the digit of disks unfilled in the cluster. So it
permanently queries the registry to make this in rank. The “Cluster Disk Selection” dialogue box will be displayed to
excellent the cluster CD-ROM on which the SQL Databases will be installed as publicized in Figure 1.3:




FIGURE 1.3 Cluster Disks selection pro SQL Server Databases.

This in rank in this area the disks is retrieved from the following location in the registry:



HKEY_LOCAL_MACHINE\CLUSTER\Resources\{GUID of the Resource}.



A function will be executed from the SQL Setup to discover all the assets pro which the Resource Type is “Physical Disk”.
The first name of the Disk is indicated by a registry access called “Name=disk_name”. Inside Figure 1.3 you can think it
over SQL Server Setup wizard has found two disks unfilled in the cluster. The not more than map shows the registry
entries produced pro a Physical Disk Resource:




FIGURE 1.4 Cluster Disks stored in Registry.



The GUIDs publicized higher than are retrieved programmatically by the SQL Server Setup Wizard. Setup will filter all the
assets pro type=Physical Disk. This catalog will be presented to the SQL Server Setup screen to excellent a CD-ROM pro
the SQL Database. Please annotation single the Disks with the intention of are online will be displayed in the SQL Server
Setup wizard. For model, if here are 3 disks in the cluster and 1 is offline pro approximately wits. The Setup Wizard will
single trade show two disks. Thus you must permanently check the cluster pro disks on which you are vacant to install
the SQL Databases.



If you always run into one conundrum or SQL Server Setup doesn’t trade show the disks accurately try to check the
higher than registry access pro disks or commence the Cluster Administrator. Please annotation, creating CD-ROM assets
manually in the higher than registry location will not help. Because as the IsAlive interval pro Physical Disk expires, a
query will be executed to check the status of the CD-ROM. IsAlive checks to think it over if the CD-ROM is operating
normally. If not, IsAlive will take the CD-ROM offline or the CD-ROM will be considered to be inflicted with disastrous.
The PersistentState regard indicates the disks status (1=online and 0=offline) as publicized in Figure 1.4.
After you be inflicted with selected the Cluster Disk pro SQL Databases, the Setup asks you to enter the Virtual Server IP
Information as publicized in not more than Figure 1.5:




FIGURE 1.5: SQL Virtual Server IP Information



The in rank entered at this time will be recorded shortly in the registry and using this in rank the SQL Virtual Server will
be assigned an IP Address pro clients to access the SQL occasion ended the arrangement. You notice lone business at
this time; the SQL Setup furthermore gets a catalog of interfaces unfilled in the cluster. The SQL Server Setup can
furthermore make a catalog of interfaces from the Network Connections folder in the logic but it doesn’t. Instead it
queries cluster list or registry to make this in rank. The registry access pro Network Interfaces is located by the following
location:

HKLM\Cluster\Networks




FIGURE 1.6: Cluster Network Interfaces catalog
After you excellent the Cluster Disk pro SQL Databases, you will be presented with the catalog of nodes unfilled in the
cluster. SQL Server Cluster Setup allows you to configure the nodes to be cluster-aware pro SQL Virtual Server Instance
you create. The Setup doesn’t be inflicted with this in rank. It permanently queries the cluster configuration list by the
following registry location to discover the unfilled nodes in the cluster:

HKEY_LOCAL_MACHINE\CLUSTER\Nodes




FIGURE 1.7: SQL Server Setup wizard and SQL Nodes.



The Setup executes a query hostile to the higher than registry answer to retrieve a catalog of nodes in the cluster. The
node first name is retrieved from the NodeName registry access as publicized in the higher than map.



After setup process has collected the higher than in rank it starts photocopying the SQL binary records on C:\ drive (this
path can furthermore be changed) and the SQL list records on the drive you selected all through the setup.



Conclusion

Inside this article we proverb the SQL Server Cluster Setup domestic process. This article explained the means SQL
Cluster Setup DLL (SQLCluster.DLL) uses to discover the catalog of nodes, disks and interfaces in the cluster. Inside the
then article of this run we will think it over troubleshooting techniques, registry entries and records which are valuable
in the failover process. We will furthermore think it over how the SQL Cluster Setup process configures a node to be
cluster-aware.

								
To top