Failover Clustering and Network Load Balancing Team Blog
So they asked me to write for a blog. Well, I’m new here, and what can a new guy write about? The basics! But the target audience for this blog is not the faint of heart, so, let’s start with a NEW basic thing for everybody: “Creating a Cluster in Windows Server 2008”.
First a small introduction:
Clustering is available in Windows Server® 2008 Enterprise and Windows Server® 2008 Datacenter editions. The improvements to failover clusters (formerly known as server clusters) are aimed at simplifying clusters, making them more secure, and enhancing cluster stability. Cluster setup and management are easier with the new MMC Snap-In management interface, and complexity is reduced by providing the user with a simple interface to create, manage and use their failover cluster. Setup is more straightforward, with fewer steps and less configuration. Also, Cluster setup is fully scriptable so that you can automate your deployment. Security and networking in clusters have been improved, as has the way a failover cluster communicates with storage.
Does your current hardware works? Just run the new validation wizard. It will run tests to determine whether your system, storage, and network configuration is suitable for a cluster. These tests include specific simulations of cluster actions, and fall into the following categories: System Configuration tests, Network tests and Storage tests.
What else is new? Well, GUID partition table (GPT) disks and partitions of up to 2 TB are supported in failover cluster storage. And, if you’re like me, you’re asking what is a GPT? Here is the answer: GPT disks provide increased disk size and robustness. 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. With failover clusters, you can use either type of disk.
Validating a Potential Cluster Configuration:
Ok, so let’s start with this cluster business. I’ll create a simple cluster to show you the reduced numbers of steps. Let’s suppose you have two servers, running Win2k8 Enterprise already, with the “Failover Clustering” feature installed. So, hit Start, type failover, and there it is, the management interface, just hit enter. (Off topic: I love this new Start Menu, don’t you?)
And then, the new MMC Snap-In for “Failover Clustering Management” appears:
These is your main “Cluster Control Panel”. From here you can create, manage and even shutdown your cluster, along with a lot of other options. This is also where you can run the Validate a Configuration Wizard, to make sure your servers’ hardware conform to the basic requirements. As a best practice, we’ll do this first to make sure the hardware configuration will work and be supported.
Just click the link Validate a Configuration… and the new Validate a Configuration Wizard appears. This info page remind you of the tests that will be performed and has links on how to prepare your hardware.
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). Again, select Next and you will have a review page, listing your servers and all tests that will be performed on them.
Hit Next and it starts! See it running on my second server:
This can take some time. Cofee anyone?
When it’s done, you see a new page, with a review of all tests, and can hit the View Report button, to get a nicely formated web page, with all tests details, like below:
A copy of this report is stored in your %windir%\cluster\reports directory if you need to access it later.
OK, so as expected your hardware is perfectly clusterable. What? Some issues? Failed? OK, there is a link on the tests review page that explains the validation tests and gives you some hints of what to do. This part is done, hit finish and we are back on our “Cluster Control Panel”.
Creating a Cluster
So, hit the link Create a Cluster…, and the Create Cluster Wizard appears, with some useful information regarding clustering. After reading, hit Next and the fun begins. This is where you will enter the servers that will participate in your “soon-to-be-formed” cluster (remember this in W2k3?). Just put the name and hit add for each one of them. I already did it for my two test machines:
Once you are done listing your servers (you can even put just one, but that is not a cluster, isn’t it?), hit Next, and the new validation screen appears, asking if you want to validate your configuration. Select No, as we already know our servers passes all tests.
So here it is finally, your cluster name. This is how everybody in your company/store/business, will access your cluster (consequently your file server). Give it a comprehensive name (my is SIbagy-FileServ) and hit Next.
See below the name? Wow, that’s great! Everything is setup automatically for us! Didn’t I tell you we have a more straightforward interface, with fewer steps and less configuration?
So we get to a review page, with our cluster name, the nodes that will participate on it, even the IP addresses! Hit Next.
Some time passes by, some messages, some blue bar filling up and…
We created a new cluster! You can even check a detailed report with the View Report button. When you press Finish, you go back to our Cluster Control Panel, with our two-node cluster created and ready to configure a highly-available service or application.
I will be describing how to set up a simple file server in my next post, so stay tuned for more fun next time I blog to you guys.
Great & Helpful post!
Thanks Symon for sharing it with us. I will give it a try!
Very informative. I successfully built a cluster at work using this method, now everyone thinks that i'm an "expert" in clustering. Thanks... I think. :)
Dear People ,
I would like to know where I can find information to setup a failover cluster using iSCSI, please let me know
Thanks in Advance
Hi Cluster Gurus
Our current Exchange cluster node are all using local disk for C drive (100GB) and D drive (180GB).
The OS is installed on the C drive and the Exchange software is installed on the D drive.
We want to add another node in the cluster, with local disk for the C drive (40GB instead of the 100GB like the other nodes) and SAN disk for D drive (instead of local disk like the other nodes).
Can we do this? If memory serves me well, in a clustered environment, all the server hardware, disk size, disk allocation, memory and CPU have to be the same?
If we lose the SAN connection and Exchange is installed on the SAN instead of the local disk, will it crash the server? Will Exchange come back online when the SAN connection comes back?
Etude et mise en place d’un serveur Web en haute disponibilité et répartition de charge sous Windows Server 2008 »
Cahier des charges
La solution mise en place devra :
- Etre virtualisée pour économiser sur le coût du matériel
- Permettre une administration souple
- Offrir une sauvegarde aisée des données
- Offrir un retour sur incident de moins de 15mn en cas d’attaque
J'aimerai avoir des informations la dessus et comment faire????????
You can find step-by-step pdf's on www.gidit.be
I have 5 guest machine and 2 host (physical server HP DL380G7) with good hardware (32GB+32GB ram) configuration.. Now i want to configure 5 VM on both host and after this process i want configure HA....
Please if you have any chance please tel me steps by steps process so i can configure this error free
Hello i would like to know what is the requirement for fail over cluster ? does we need to shared storage for making fail over cluster ?
1.The node should be on the same network?
2.Can we connect node in wide area for creating fail-over clustering ?
I want to understand the concept of clustering and nodes, may I know the best site for this?
I have one Win Svr and two systems, I want clustering on my both systems so do I need to buy one more svr or I can cluster with my one Win Svr on two machines?