While this might seem like a simple decision, the consequences can directly affect the future availability of the cluster.
Most people tend to under estimate their storage needs which presents several problems.
We have a 3 node Windows 2008 R2 cluster on UCS blades.
There are 54 cluster disks attached with SQL instance data on them.
This article will examine the various storage components that need to be considered when designing, installing and configuring failover clusters, and how to avoid the common pitfalls that affect stability.
Perhaps one of the biggest decisions to make when installing a Windows Failover Cluster is the size of the storage partitions.
The fault tolerant design of clusters ensures there is no single point of failure including multiple servers, multiple network connections and multiple storage controllers.
The trade-off that you pay for this high availability is the additional layer of complexity involved with installing, configuring, and troubleshooting issues.
What would be the result of clearing the reservations on active cluster LUNs?
Related: Windows Server 2012 R2 Failover Clustering When the Cluster Service starts, it detects the networks on a node, then identifies the network cards in each network.
A common problem that I've encountered is that people are unaware that Windows Server Failover Clustering (WSFC) allows only one network card on a node in the same network. For example, suppose an administrator, Bill, configured a node with two cards in the same network: Card1 IP Address: .1 Subnet Mask: 255.0.0.0 Card2 IP Address: .2 Subnet Mask: 255.0.0.0 The Cluster Network Driver (Netft.sys) will use only one network card (or team) per network.
Specifically, GPT disks can have partitions larger than two terabytes (that’s a lot) and have built-in redundancy in the way partition information is stored, unlike master boot record (MBR, bye old friend) disks.
Once read, hit Next and select all the tests (additional storage devices and nodes exponentially increase the time to completion, so if, for example, you have tested the storage before you may want to skip it).
As a result, I've had to troubleshoot quite a few problems.