Identify and resolve SQL Server problems BEFORE they happen with SQL diagnostic manager

SQL Server Post Cluster Configuration Checklist (Part 2 of 4)

By: Chad Boyd | Read Comments | Print Chad is an Architect, Administrator and Developer with technologies such as SQL Server, .NET, and Windows Server. Related Tips: More

This is the second checklist in the process – run through it just after you form the cluster, or prior to installing SQL Server in any environment.

Server Cluster Post-Installation Checklist

Check	Pass	Fail
Create MS DTC and configure completely
Verify priority of cluster network(s) - all Private networks have priority over Public
Verify Quorum disk configuration (location, log size)
Disable NetBIOS for Cluster IP Address
Verify all the server cluster IP addresses can be resolved inside and outside of the server cluster
Verify the server cluster’s name can be resolved inside and outside of the server cluster
All groups containing disk resources can fail over to all nodes
Verify the Cluster Group resource group can fail to all nodes
Verify the MSDTC resource group can fail to all nodes
Increase the cluster log size
Kerberos enabled (if needed; requires Windows 2000 Service Pack 3 or higher or Windows Server 2003)
If antivirus software is installed, set filter to exclude the \MSCS directory on the quorum, all Sql extensions, Sql Server program files path, large ETL paths, etc.
Verify minimum of 2 cluster networks configured to support internal cluster communications
Verify all cluster network configurations (communications)
Verify cluster registry entries were written correctly (HKLM\Cluster)
Verify event logs do not contain errors or warnings, especially with relation to the ClusSvc.  Ensure entries exist stating confirmation of forming/joining of/to cluster

 

Related Tips: More | Become a paid author

Last Update: 6/29/2008

Share:

Share

Tweet

Free SQL Server Learning Building Blocks for Your SQL Server Career Database development best practices What Are You Waiting For?

Comments and Feedback:

Post a Comment or Question

Keep it clean and stay on the subject or we may delete your comment.
Your email address is not published. Required fields are marked with an asterisk (*)

*Name

*Email

Notify for updates

Comments *** NOTE *** - If you want to include code from SQL Server Management Studio (SSMS) in your post, please copy the code from SSMS and paste the code into a text editor like NotePad before copying the code below to remove the SSMS formatting.
*Enter Code

 

Sponsor Information

"SQL doctor ROCKS! As soon as I ran it, problems that have been giving me headaches were identified and cured." Web-based SQL Server monitoring whenever, wherever. You don't know, what you don't know about SQL Server... Customized Consulting and Training Solving SQL Server problems for millions of DBAs and Devs since 2006. Join now. The SQL Server Security THREAT - It’s Closer Than You Think