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 |
|
|
About Chad Boyd
Chad is an Architect, Administrator, and Developer with technologies such as Sql Server (and all related technologies), Windows Server, and Windows Clustering. He currently works as an independent consultant and also spends a significant amount of time writing, talking, presenting and blogging about Sql Server in person and online at http://mssqltips.com. In the past, Chad has worked with companies and organizations such as Microsoft Corporation and The American Red Cross, and provided consulting/support services at companies such as Bank of America, HP, Citigroup, Qualcomm, Scottrade, TJX, SunTrust, and Zurich Financial Services. For over 3 years with Microsoft Corporation Chad was responsible for providing onsite and remote support, guidance, and advice with SQL Server products to some of Microsoft’s foremost enterprise customers running the largest, most complex SQL Server installations and configurations in the world. This included all SQL Server products and versions, including SQL Server 7.0, 2000, 2005, and recently 2008, the SQL Server database engine, Reporting Services, SSIS/DTS, Notification Services, and Analysis Services on both 32 and 64 bit systems. Chad's primary responsibilities today include troubleshooting critical server situations, performance tuning and monitoring, disaster recovery planning and execution, architectural guidance for new Sql Server related deployments, and delivering deep technical workshops/presentations/proof-of-concept sessions covering a variety of technologies and functionality. Chad regularly posts Sql Server related content, tools, and advice with the mssqltips team at http://blogs.mssqltips.com/blogs and http://mssqltips.com. Chad can be contacted via his blog or email at chad dot boyd dot tips at gmail dot com.
