Hi All
I'm struggling to find some good documentation on how to
place SQL ersources in the cluster groups.
Wuold I be correct in saying the following:
1) Place the Quorum and MS-DTC resources in a cluster
group together.
2) Place all other SQL and Windows resources in another
cluster group together?

The Quorum resource sits on it's own Q drive. All SQL data
sits on the F drive.

Thanks in advance for any help.
J

Hi J,
let me add in a few practices that I use for my clusters:
a) the shared storage should be using SCSI disks with RAID
protection.
b) The quorum resource should be on an entirely different
physical disk set (meaning different sets of hard disks)
from SQL resources.
That is, the quorum and SQL resources should not be in
the RAID array at all.
In my case, my quorum sits on a RAID1 array.
c) The SQL logs and data files should also sit on
different logical drives (eg S: for Logs and T: for Data).
Better yet, they use different disk sets or RAID arrays.
The reason is that one is written sequentially while
the other is written in parallel. Cannot remember which is
which though 8-P
d) Disable NETBIOS for the private network cards. This
will prevent external network requests from interfering
with the cluster communication.
e) If you have yet another network card for backups like I
have, add the IP address and Backup Network name in a
separate cluster group. (eg server name is DBA1 and its
backup name is DBA1BK)
Reason is so that if the backup network fails but main
network is still okay, the SQL resources will not cause
the SQL resources to failover to the othe node
unnecessarily.

Hope this helps!

Benny Koh
DBA
TECH Semiconductor Singapore

See comments in line.

This is okay.

Only the SQL Server related resources (i.e. those created
by the SQL install plus any additional disk resources you
may add for SQL Server to use) should be in the same
group. 'Other Windows resources', if any, should not be
placed in the SQL Server resource group. Especially there
shouldn't be any unnecessary dependencies that may cause
problems for the SQL Server resources.

Linchi

Hi Linchi
Thanks for that. When I mean "other resources", I'm
talking about the Windows cluster resources.
Should I put MS-DTC, Quorum and other windows cluster
resources together and the SQL resources all in their own
cluster group? I understand that the cluster group's
resources will all fail-over together but I'm not sure
how/why to seperate the resources into these groups. Is it
base on dependencies?
Thanks
J

Thanks Benny

Hope you're still monitoring the thread :-)

The msdtc can reside in the cluster group but you need to
think twize before placing the msdtc log files on the
quorum disk. If you use msdtc a lot this could cause
serious cluster problems. MOM is a typical case which
recommends at least 512 MB for the msdtc log. The quorum
disk should be cared for!

"Other resources":
All resources for a virtual server should be in the same
cluster group. That is Network Name, IP, Disks, SQL Server
and SQL Server Agent. You havn't got much of an
alternative either as there are dependencies among them.
You cannot have cross-group dependencies.

SQL Server setup does all this for you. All resources will
be created in the cluster group where the data disk is
located.

HTH