- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Windows Server 2003
- >
- Clustering Windows Server 2003
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-21-2004 08:41 AM
тАО06-21-2004 08:41 AM
Clustering Windows Server 2003
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-21-2004 05:30 PM
тАО06-21-2004 05:30 PM
Re: Clustering Windows Server 2003
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-21-2004 10:59 PM
тАО06-21-2004 10:59 PM
Re: Clustering Windows Server 2003
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-22-2004 11:58 PM
тАО06-22-2004 11:58 PM
Re: Clustering Windows Server 2003
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-28-2004 09:01 PM
тАО06-28-2004 09:01 PM
Re: Clustering Windows Server 2003
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?