We help IT Professionals succeed at work.

Server 2003 R2 Clustering

Medium Priority
620 Views
Last Modified: 2013-11-15
We need some basic setup assistance for Microsoft Server 2003 clustering, actually Server 2003 R2 64-bit Enterprise Edition clustering.

SETUP: Single Domain, two DCs and one member server.  This is flexible (we could demote one DC and cluster two member servers).  Each machine has one (not two) NICs.

GOAL: Two-node IIS cluster

PART 1:
Looking for some step-by-step (by the numbers) documentation.  Another answer here on Experts-Exchange has something like this but the links are bad.

PART 2:
Here is what we’ve done so far:
When we created the quorum we got a warning about no sharable quorum resource.
Then, we got the message a multinode cluster can not be created because the quorum resource does not support adding nodes to the cluster and the quorum disk can not be located by the cluster service.

We want to get the cluster working first and then add the IIS.

Comment
Watch Question

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Technology and Business Process Advisor
CERTIFIED EXPERT
Most Valuable Expert 2013
Commented:
With a few exceptions, clustering REQUIRES a SHARED disk.  It also is usually necessary to have TWO NICs for the system, one as a heartbeat and the other as the network connection.

You're porbably better off with a load balancing situation here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;816111

Author

Commented:
You mentioned  "REQUIRES a SHARED disk"
Just what precisely does this mean?

Do we need a third machine on the public network with an NTFS file share as the shared disk?

Lee W, MVPTechnology and Business Process Advisor
CERTIFIED EXPERT
Most Valuable Expert 2013

Commented:
I mean a SAN system, External SCSI enclosure, iSCSI storage unit or some kind of storage device that can connect to the cluster for quorum.  You may be able to use 2003's majority node set quorum ability, but again, I think, if your purposes are redundancy in web services, you are better off using a load balancing.
I would agree... usually in a web environment, you would using Network Load Balancing.
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.