Quorum Drive

Hi,

We have SAN configured below intended for SQL 2005.


A. Raid Group 1 - 6 SAS disk (300GB each) configured as RAID 1+0
a. Volume 1 - Data - 500 GB
b. Volume 2 - Quorum - ????? or on RG2?????
B. Raid Group 2 - 2 SAS disk (300GB each) configured as RAID 1
a. Volume 1 - Logs - 367 GB
b. Volume 2 - Quorum - ????? or on RG1?????


Where should we put our Quorum for the Cluster???
Or should we follow recommendation of MS that Qurum must be on separate Raid
Group???
Is 1 GB size okay for the Quorum???

Windows 2003 Cluster requires a minimum of 500 MB for quorum. I would
create a LUN as small as possible; these days 1 GB may be that number for
you. Regarding the groups in cluster administrator.. You want all the
groups in your cluster to configure so that they can fail over
independently of one another. I would consider creating the cluster group
containing:

[Cluster Group]
Cluster Virtual Network Name (Name should be dependent on IP)
Cluster IP address
Quorum Disk
MSDTC (should be dependent on Network Name and quorum disk)

[SQL Group]
Physical disk resources for Logs and Data
SQL resources
Virtual network name for SQL

In this way, these two groups are isolated from each other.

Dave Guenthner [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Thanks Dave!

When installing the SQL in Cluster where should be the location of
installation files??? Local Disk or Physical Disk Resource???




"Dave Guenthner [MSFT]" <> wrote in message
news:...
> Windows 2003 Cluster requires a minimum of 500 MB for quorum. I would
> create a LUN as small as possible; these days 1 GB may be that number for
> you. Regarding the groups in cluster administrator.. You want all the
> groups in your cluster to configure so that they can fail over
> independently of one another. I would consider creating the cluster group
> containing:
>
> [Cluster Group]
> Cluster Virtual Network Name (Name should be dependent on IP)
> Cluster IP address
> Quorum Disk
> MSDTC (should be dependent on Network Name and quorum disk)
>
> [SQL Group]
> Physical disk resources for Logs and Data
> SQL resources
> Virtual network name for SQL
>
> In this way, these two groups are isolated from each other.
>
> Dave Guenthner [MSFT]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>

I would copy the flat/source files locally to node 1. When running SQL
setup in a cluster, SQL will install to Node 1 and create a scheduled task
on Node 2 to install binaries there as well. You want to have the physical
disk resources available and online in cluster administrator in SQL group
before running SQL Setup.

Dave Guenthner [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Thanks Dave for this very helpful information!



"Dave Guenthner [MSFT]" <> wrote in message
news:z02VhS$...
>I would copy the flat/source files locally to node 1. When running SQL
> setup in a cluster, SQL will install to Node 1 and create a scheduled task
> on Node 2 to install binaries there as well. You want to have the
> physical
> disk resources available and online in cluster administrator in SQL group
> before running SQL Setup.
>
> Dave Guenthner [MSFT]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>