|
3.482 bytes |
Service Hints & Tips |
Document ID: MCGN-3UGREJ |
Servers - ServeRAID II and SQL Server Cluster setup configuration
Applicable to: World-Wide
Microsoft SQL Server, Enterprise Edition, version 6.5
-----------------------------------------------------------------------------
SYMPTOMS:
The SQL Server Cluster setup wizard may fail to correctly identify the disk volume that SQL Server has installed. This happened when the volume is controlled by a third-party custom written resource DLL. IBM ServeRAID Logical Disks are one such example.
CAUSE:
The SQL Server Cluster Setup looks for SQL Server to be installed on a resource type "Physical Disk". Any other resource type will fail, even though it is a mass storage device that SQL Server has installed.
WORKAROUND:
The workaround involves modifying the registry to 'fool' the SQL Server Cluster Setup Program.
When using the IBM ServeRaid adapter the disks will not fail-over to the other cluster properly. Therefore the resource type must be changed several times to get SQL Server Cluster setup to work.
WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor.
Use Registry Editor at your own risk.
For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).
Locate the following Key:
HKEY_LOCAL_MACHINE
\Cluster
\Resources
Within this key you will see several other keys in a binary GUID fashion. They follow this structure: 12354678-1234-1234-1234-1234567890ab
Highlight each one individually and look on the right-hand pane. Notice the Type value. Look for the name of your third-party disk resource and change it to "Physical Disk". This is case sensitive.
Now repeat this procedure on the other node of the cluster.
You can now run the SQL Cluster Setup. In some cases you will need to change this back to the original resource type before failing the disk over to the other node.
|
Search Keywords |
| |
|
Hint Category |
Microsoft Cluster Server | |
|
Date Created |
14-05-98 | |
|
Last Updated |
29-10-98 | |
|
Revision Date |
22-10-99 | |
|
Brand |
IBM PC Server | |
|
Product Family |
Netfinity 7000, PC Server 325, PC Server 330, PC Server 704, PC Server 720 | |
|
Machine Type |
8651, 8639, 8640, 8650, 8642, 8641 | |
|
Model |
Various | |
|
TypeModel |
| |
|
Retain Tip (if applicable) |
| |
|
Reverse Doclinks |