SQL Server Performance

Cluster Design Help

Discussion in 'SQL Server Clustering' started by suniljk, Feb 27, 2007.

  1. suniljk New Member

    Here we are planning for clustering of Sql2000 on windows 2003, i have some doubts on the planning of this.<br /><br />1) i have only one shared array (Raid5) with 500GB so my plan is to do logical partition on this which will look like:<br />Q<img src='/community/emoticons/emotion-2.gif' alt=':d' />rive 20 GB (for Quorum drive)<br />D<img src='/community/emoticons/emotion-2.gif' alt=':d' />rive 250 GB (for data)<br />L<img src='/community/emoticons/emotion-2.gif' alt=':d' />rive 100 GB (for log)<br />B<img src='/community/emoticons/emotion-2.gif' alt=':d' />rive 80 GB (for backup)<br />M<img src='/community/emoticons/emotion-2.gif' alt=':d' />rive 10 GB (for MSDTC) for later use if required.<br /><br />Now am using this drive Q for Quorum drive and D for data and L for log like this..<br />is this a good method to work or do we need to go for different physical disk for Quorum drive? (i read this is good and possible method)<br /><br />2) In my cluster setup we are not using any distributed transactions so is it necessary to install MSDTC. My plan is not to install MSDTC and if it is required later i can install later.<br /><br />3) because there is some compatability issue with sql 2000 and windows 2003 we must install service pack 4 after cluster installation, is there any special care i have to give when i install sql2000 on win 2003.<br />
  2. Argyle New Member

    1.<br />No. Clustering work at RAID array level, not at the logical partitions. You can not create one big array and create logical partitions on it if you intend to use it for clustering.<br /><br />The Q<img src='/community/emoticons/emotion-2.gif' alt=':d' />rive must be its own raid, normaly a RAID1 of two smaller disks. The same goes for Data and Log drives.<br /><br />If you have low MSDTC usage put it on same drive as quorum.<br /><br />Example, you have an array with 8 disks:<br />Q: RAID1 - 2 disks - Qurorum and MSDTC<br />E: RAID5 - 4 disks - SQL Data and Backup<br />F: RAID1 - 2 disks - SQL Log<br /><br />If you are really low on disks you could combine data, backup and log on same array, prefferably a RAID1+0. You need a minimum of two arrays, one for quorum and at least one for SQL Server.<br /><br />2.<br />You should install it from start. You can configure it to use the same name, ip and disk as the default cluster group that contiain the Q<img src='/community/emoticons/emotion-2.gif' alt=':d' />rive.<br /><br />3.<br />The service pack 4 readme have specific instructions for cluster install. Follow those and you should be fine.
  3. suniljk New Member

    <blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><i>Originally posted by Argyle</i><br /><br />1.<br />No. Clustering work at RAID array level, not at the logical partitions. You can not create one big array and create logical partitions on it if you intend to use it for clustering.<br /><br />The Q<img src='/community/emoticons/emotion-2.gif' alt=':d' />rive must be its own raid, normaly a RAID1 of two smaller disks. The same goes for Data and Log drives.<br /><br />If you have low MSDTC usage put it on same drive as quorum.<br /><br />Example, you have an array with 8 disks:<br />Q: RAID1 - 2 disks - Qurorum and MSDTC<br />E: RAID5 - 4 disks - SQL Data and Backup<br />F: RAID1 - 2 disks - SQL Log<br /><br />If you are really low on disks you could combine data, backup and log on same array, prefferably a RAID1+0. You need a minimum of two arrays, one for quorum and at least one for SQL Server.<br /><br />2.<br />You should install it from start. You can configure it to use the same name, ip and disk as the default cluster group that contiain the Q<img src='/community/emoticons/emotion-2.gif' alt=':d' />rive.<br /><br />3.<br />The service pack 4 readme have specific instructions for cluster install. Follow those and you should be fine.<br /><hr height="1" noshade id="quote"></font id="quote"></blockquote id="quote"><br /><br /><br />Thanks for the reply! but i have only 1 RAID5 array, so i can't partition it for Quarum and Data disk... i have to use RAID1 for Qurorum..<br /><br />But for data, log and backup i have create partion in the RAID5 arrary and allot one one partition for each.. this will work na?
  4. Argyle New Member

    You can have:
    Q: RAID1 - 2 disks - Qurorum and MSDTC
    E: RAID5 - X disks - SQL Data, Log and Backup

    There is no need to logicaly partition the RAID5 volume. You gain more space flexibility with 1 logical partition.

    You can't have:
    Q: RAID5 - X disks - Quorum, MSDTC, SQL Data, Log and Backup

    It's not a supported configuration by Microsoft.
  5. suniljk New Member

    quote:Originally posted by Argyle

    You can have:
    Q: RAID1 - 2 disks - Qurorum and MSDTC
    E: RAID5 - X disks - SQL Data, Log and Backup

    There is no need to logicaly partition the RAID5 volume. You gain more space flexibility with 1 logical partition.

    You can't have:
    Q: RAID5 - X disks - Quorum, MSDTC, SQL Data, Log and Backup

    It's not a supported configuration by Microsoft.


    so we can't use one single RAID5 (array) for all Quorum, MSDTC, SQL Data, Log and Backup
    we need to have minimum 1 Separate disk for Quorum.
  6. suniljk New Member

    quote:Originally posted by Argyle

    You can have:
    Q: RAID1 - 2 disks - Qurorum and MSDTC
    E: RAID5 - X disks - SQL Data, Log and Backup

    There is no need to logicaly partition the RAID5 volume. You gain more space flexibility with 1 logical partition.

    You can't have:
    Q: RAID5 - X disks - Quorum, MSDTC, SQL Data, Log and Backup

    It's not a supported configuration by Microsoft.



    Is there any microsoft link saying this....
  7. Argyle New Member

    It is possible to force the sql server data onto the quorum disk but you will get a warning during install that you should not configure databases on the same drive
    as the quorum drive.

    It does present a higher risk since a failure to any service will cause failure of the entire group. So in that case you might ask yourself why are you configuring a high availibility solution in the first place if you inted to impose higher risks into the setup. But again if you have no other option you can force it during install.

    A referece:
    http://support.microsoft.com/kb/243218
    "Caution Do not select the quorum disk (the last group in the list) because the quorum disk must be treated as a special resource. A warning message appears if you select the quorum disk. For more information, see the "Quorum Disk Selection Warning" topic in SQL Server 2000 Books Online.

    When you use a small cluster, the quorum disk may be the only choice available. Use the quorum disk only for testing purposes or to explore failover clustering.

    Important Never use the quorum group for production purposes."

Share This Page