Problem adding a node to a Windows x64 2003 cluster

You can't 'share' a Quorum.

You need a shared storage option.

With a 1955 blade that means you need an iSCSI storage solution or a fibre channel storage solution.

Examples would be the Dell MD3000i, Dell|EMC AX, CX or CX3-series, or a Dell|Equallogic solution.

You'll also need fibre channel cards or extra NICs.

Hi DevMgr, thanks for that. That explains why I wasn't able to do it. We have just fitted a Dell MD300i which is to be used for other file storage purposes so going by your advice I should create a share on this instead for clustering purposes? When configuring the cluster using Cluster Administartor should I select "Majority node set" instead of "local quorum" after setting up the share? Thanks.

With an MD3000i, you create a host group, register both servers and put them in the same host group.

Now you create a virtual disk for the Quorum and map it to the host group.

After this pick 1 server and have it scan the device manager for hardware changes. After this go to disk manager and you'll see the new disk. Initialize it, but don't convert (to dynamic). Create a partition on it and give it a drive letter (Q is a common choice for the Quorum).

Now go to the other server and have it scan for hardware changes in the device manager. After this in disk management you'll see the disk as well, but it'll be unreadable. This is fine!

On the first server set up the 2003 cluster (requires being part of a domain, having fixed IPs, and requires 2003 Enterprise edition (and both servers being x86 or x64, no mixes)). After this add the 2nd node to the cluster.

Now you can fail over the cluster group from node to node using the cluster administrator.

If you're not sure how to set up a server to connect to the MD3000i, check the install guide for the MD3000i here.

Hi DevMgr,

 

Thanks for all your advice, it has been very helpful. I am at the stage now where I have created a host group and have added the two servers in MD Storage Manager. I have also created a virtual disk and now mapped it to the host group as you suggested. I will let you know how I get on from here. Many thanks!

Hello again,

 

I followed the rest of your instructions and have managed to configure a Windows Cluster which successfully fails over so everything looks fine! Thanks very much.

 

During the Cluster Administration however there was no prompt about selecting a NIC to use as the heartbeat? Did I miss something there or is it all taken care of automatically because it is a virtual disk?

 

I also need to set up a 2nd cluster using another two blades. This cluster will also include SQL server 2005. Do I need to install SQL server on the two blades that I am using in the cluster or should I install SQL server on the  new virtual disk "Q" drive? Thanks.

 

 

Go into the cluster administrator. Right click the cluster (first entry in the tree on the left side) and go to properties.

In here go to the network tab. This is where you set your cluster's internal communication priority. The heartbeat should be at the top and then any links going over your public network (in case the crossover cable gets disconnected it'll use the public network as the heartbeat's backup).