Reference Guide

Preparing Your Systems for Clustering 33
Creating a LUN for the Quorum Resource
It is recommended that you create a separate LUN—approximately 1 GB in
size—for the quorum resource.
When you create the LUN for the quorum resource:
• Format the LUN with NTFS.
• Use the LUN exclusively for your quorum logs.
• Do not store any application data or user data on the quorum resource.
• To easily identify the quorum resource, it is recommended that you assign
the drive letter "Q" to the quorum resource.
NOTE: The Majority Node Set Quorum types for Windows Server 2003 are not
supported.
Preventing Quorum Resource Failure
Since the quorum resource plays a crucial role in cluster operation, losing a
quorum resource causes the entire cluster to fail. To prevent cluster failure,
configure the quorum resource on a RAID volume in the shared storage system.
NOTE: It is recommend that you use a RAID level other than RAID 0, which is
commonly called striping. RAID 0 configurations provide very high performance, but
they do not provide the level of availability required for the quorum resource.
Configuring Cluster Networks Running Windows Server 2003
When you install and configure a cluster running Windows Server 2003, the
software installation wizard automatically configures all networks for mixed
(public and private) use in your cluster. You can rename a network, allow or
disallow the cluster to use a particular network, or modify the network role
using Cluster Administrator. It is recommended that you configure at least
one network for the cluster interconnect (private network) and provide
redundancy for the private network by configuring an additional network for
mixed (public and private) use. If you have enabled network adapter teaming
or are using dual-port NICs for use on your public network, you should change
the configuration for these networks to support public communications only.