best practices to deploy MS SQL clusters and network settings

Hi Experts,

I have 2 clients who are running into some clustering issues, and recently NICs on different servers of the same cluster failed. Each client runs following infrastructure:


Client 1

Windows 2008 R2 cluster conformed by 3 physical nodes. OS is Windows 2008 R2, SQL version 2008

Client 2

Windows 2012 R2 cluster with 3 physical nodes. OS is WIndows 2012 R2 SQL version is 2012

All machines are physical, run in a Windows 2008 R2 forest and domain functional level

My questions are:

What are the recommended hotfixes to deploy on Windows 2008 R2 and 2012 R2 physical cluster for SQL?

What are the best practices and recommended settings for NICs on all the 3 nodes?

What are the recommended settings for building the cluster following MS best practices?

This client runs multiple SQL instances, any thoughts?

Your feedback is highly appreciated
Jerry SeinfieldAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Ryan McCauleyEnterprise Analytics ManagerCommented:
Are you asking about building new clusters, or about ensuring the current ones are in good health?

We run about a dozen MSSQL instances on each of our failover clusters (both in an active/passive configuration, as well as active/active where the instances are balanced across all nodes), so no concerns there.

For updates, I'd honestly recommend that it be as up to date as possible - if you have a testlab or a standby cluster that you can patch first (to confirm that everything works as expected), that's ideal, but not something everybody has available. I'd encourage you to stay up to date on patching - even if you're a month back to ensure that you don't deploy anything problematic, being any further back than that leads to potential security issues on the servers.

Are the network drivers up to date, and do you have separate network connections for the public and heartbeat networks? While you can run the heartbeat connection over the same card and switch as your public (client traffic) network, it's highly encouraged that it be a separate NIC and either a VLAN segment of your switches or a cross-over cable (since you have three nodes, a cross-over cable doesn't work for you - that's a two-node solution). With a dedicated heartbeat network connection, they have unrestricted access to each other in the case of a network failure, and they can more easily figure out which node should be in charge of specific resources. Many cluster failures I've seen are a result of dropped network connectivity - if no nodes can see any others (if they lose the heartbeat network), then nobody will claim ownership of the resources.
Jerry SeinfieldAuthor Commented:
thanks, yes, we do have separate networks for production and heartbeat

Can you or someone else please advise on the recommended hotfixes, and NIC settings? speed, IP4 properties, and so on
EugeneZ ZhitomirskySQL SERVER EXPERTCommented:
make sure you have latest OS and Sql server service packs;
the rest is "normal"
BTW: did you run "Cluster verification \tests"? Did all PASS?

please verify by reading these MS posts
Windows Server 2008 Failover Clusters: Networking (Part 1)
http://blogs.technet.com/b/askcore/archive/2010/02/12/windows-server-2008-failover-clusters-networking-part-1.aspx

Windows Server 2008 Failover Clusters: Networking (Part 4)
http://blogs.technet.com/b/askcore/archive/2010/04/15/windows-server-2008-failover-clusters-networking-part-4.aspx


and (just in case)

Before Installing Failover Clustering
https://msdn.microsoft.com/en-us/library/ms189910(v=sql.105).aspx

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.