topic Clustering Windows Server 2003 in Windows Server 2003

Clustering Windows Server 2003

Wil robbins — Mon, 21 Jun 2004 15:41:54 GMT

Have 2 LP 2000r dual processor servers, connected to an RS/12 by Netraid 4M controllers. Win2K3 (ent) set up on both servers just fine.
NetRaid Boot Utility used to configure Netraid controllers for Cluster as prescribed for Win2K clustering and in the Netraid UsersGuide.
Used FAST to define and verify disksets and containers Quorum(2x9GB HP Drives-RAID 1), and Application (5x18.5GB HP Drives-RAID 5).
Formatted each in Disk Management under Win2K3 OS as primary NTFS partitions labelled Q and R respectively. Set up Cluster in Win2K3, while sees drive Q, when select it for shared quorum says NO drives hosted, so configuration defaults to local quorum on C drive.
Need to resolve issue of No drives hosted. Also, if try to change local quorum to shared quorum, sees drive Q but needs a partition name. I can not figure out how to name the partition. There is only one so thought it would default to either the disk letter (Q:) or the volume label "Quorum". Anyone have any ideas???
thanks,
Wil

Re: Clustering Windows Server 2003

Rune J. Winje — Tue, 22 Jun 2004 00:30:11 GMT

In Cluster Admin - are you able to define the Q: and R: disks as Physical Disk resources?

But I think the main issue here is that NetRaid 4M is not qualified for use in Window Server 2003 cluster. (It is OK for use in Win2K cluster though).

When Win2K3 sees controllers that are qualified for Windows 2003 cluster use, the setup will progress without any problems.

Cheers,
Rune

Re: Clustering Windows Server 2003

Pieter 't Hart — Tue, 22 Jun 2004 05:59:47 GMT

i have no experience with 2003 cluster only nt4.
but i have some questions

maybe w2003 requires an emtpty space on the disk to create a new quorum-partition?

does this also happen wist system-2 down ?
with nt4 you first have to bring both systems seperately up to see the disk
then only one of the systems has access to the disk until you bring it under "cluster-command". This should be done on the system that owns the disk at that moment.

Pieter

Re: Clustering Windows Server 2003

Vincent Berendsen_1 — Wed, 23 Jun 2004 06:58:34 GMT

Hi There!

I have the same problem. (also an NetRAID 4M and Windows 2003, in this case 2 LC-2000 servers, but that can be ignored).

On the OS level the drive actually functions flawless. But the cluster Administrator keeps saying (when adding a new NetRAID4M DiskSet resource - No Partitions).

So when trying to assign the new resource as the Quorum Disk for the cluster, it halts saying it doesn't host partitions.

Also because of this, I can't add another nodeto the cluster, because they can't connect to the same quorum location (at this point still the local quorum).

I've read on this forum that some people got this configuration to work.

Can someone please tell us how?

Or does someone tell me what kind of controllor to buy (for in the LC-2000) to connect to the RS/12 that actually does work with Windows 2003? (We don't have the budget to replace all of our servers, all LC-2000's/LC-3000's)

Thanks In Advance,

Vincent

Re: Clustering Windows Server 2003

Raymond_61 — Tue, 29 Jun 2004 04:01:59 GMT

Quick question:-

You are using Win2k3 and Netraid 4m controllers. I have an lh3000 i want to upgrade to 2003 in-place - does 2k3 have the necessary drivers bundled in, or will i have to find additional drivers?