solving sql server problems for millions of dbas and developers since 2006



SQL Server DBA Tips SQL Server Developer Tips SQL Server Business Intelligence Tips SQL Server Career Tips SQL Server Tip Categories SQL Server Tutorials SQL Server Webcasts SQL Server Whitepapers SQL Server Tools SQL Server Questions and Answers MSSQLTips Authors About MSSQLTips SQL Server User Groups MSSLQTips Giveaways MSSQLTips Advertising Options

MSSQLTips Facebook Page MSSQLTips LinkedIn Page MSSQLTips RSS Feed MSSQLTips Twitter Page MSSQLTips Google+ Page





SQL Product Highlight

Red Gate Software - SQL Monitor

SQL Server performance monitoring and alerting - SQL Monitor offers an easy entrance to advanced server monitoring with a simple design that's a refreshing change from the status quo. Red Gate have added custom metrics and user roles to the product without spoiling its ease-of-use, to help you answer that timeless question, 'How healthy are your servers?'

Learn more!




SQL Server Pre Cluster Installation Checklist (Part 1 of 4)

By: | 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 first checklist in the process – run through it as soon as you are ready to form the cluster, or prior to installing SQL Server in a standalone-configuration.

Server Cluster Pre-Installation Checklist

Check Pass Fail
Verify cluster hardware configuration on Windows Catalog/HCL
Complete each of the following documents for the cluster and nodes in the cluster:-      Cluster Config.doc-      Cluster Node Config.doc-      Disk Configuration.doc-      SQL Cluster Config.doc
All to-be cluster nodes are attached to the same domain
Domain contains at least 2 Domain Controllers
Domain contains at least 2 DNS servers that support dynamic updates and configured as Global Catalog Servers
Domain Controllers are configured with at least 2 DNS servers – If DC’s are also DNS, each should point to itself for primary, and the other for secondary resolution
Minimum of two networks on different subnets configured
Private LAN isolated from all network infrastructure other than cluster nodes (including DC’s, WINS servers, DHCP servrs, etc.)
Verify ALL to-be cluster networks configured on separate subnets, distinct from all other to-be cluster networks
Public Network(s) configured to have binding priority over Private Network(s) on all nodes
Only TCP/IP configured on the private network(s); all other options unchecked
NetBIOS disabled on Private Network(s) (if not a MNS cluster)
Private network(s) do NOT contain DNS, WINS, or Gateway definitions
Private network(s) NOT configured to register with DNS
Network cards (public and private) set to a static speed and duplex on all nodes and NICs
All NICs configured with same communication settings (speed, duplex, flow control, media type)
Verify Public networks configured for Maximum Throughput of Network Applications
All public NICs configured with at least 2 DNS servers
WINDOWS 2000 ONLY – DHCP Media Sense Disabled
Disable network task offloads if possible
Verify 8.3 naming structure enabled
Verify all server node names are all UPPERCASE
No errors from hardware specific monitoring tools provided by the vendor on all nodes
Ping the local loopback address 127.0.0.1 on each node
Ping the individual IP address of each network adapter on all nodes from each other node
Ping the individual IP address of each network adapter on each node from a machine not in the cluster
Ping the name of each individual node from each node of the cluster
Ping the name of each individual node from a machine not in the cluster
Verify that all required services are running and configured for boot on all nodes
Verify cluster disks can be seen by all nodes (power each server on one at a time)
Verify the cluster disks are Basic disks, MBR, and formatted with NTFS.
Verify all disks are properly aligned and have correct offset
Ensure all the latest OS updates, security patches, and related hotfixes have been installed
Ensure local admin account has non-blank password
Verify staggered boot delay for all cluster nodes
Verify processor scheduling for background services, memory usage for programs, visual effects off
Verify appropriate page file configuration
Verify unnecessary services disabled
MSDTC service configured for network access (if MSDTC install)
Run syscomparre.exe to verify node matches (if available)
Ran ClusDiag.exe to verify node configurations
Before continuing, power down all nodes but the first node to be installed on
Turn off screen saver
Update allowed size of all event logs (Application, Security, and System)

 



Related Tips: More | Become a paid author


Last Update: 6/29/2008

Share: Share 






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
*Enter Code refresh code


 
Sponsor Information
Find and fix SQL Server problems before they happen - SQL diagnostic manager now with predictive analysis!

It takes just 5 minutes to connect your SQL Databases to source control. Got 5 minutes? Get started now.

SQL Servers keeping you up at night? Contact the Edgewood SQL Server consultants for a Health Check.

Free Trial: Get Proactive Insight with Spotlight® for SQL Server Enterprise.

Solving SQL Server problems for millions of DBAs and Devs since 2006. Join now.

Valuable SQL Server web casts on Performance Tuning, Development, Administration, SSIS and more...


Copyright (c) 2006-2012 Edgewood Solutions, LLC All rights reserved
privacy | disclaimer | copyright | advertise | about
authors | contribute | feedback | giveaways | user groups
Some names and products listed are the registered trademarks of their respective owners.


Edgewood Solutions LLC | MSSharePointTips.com | MSSQLTips.com