Drive Configuration on Dell PowerEdge 2800

Discussion in 'Windows Small Business Server' started by John Miele, May 19, 2006.

  1. John Miele

    John Miele Guest

    We currently have SBS 2000 running on a Server with a four volume
    configuration: c, d, e, and f. We are migrating to SBS 2003 on a new server
    that has the following physical configration: 7 drives(73GB each) with 1
    raid controller. Before we set up the hardware raid, I wanted to get some
    direction. My questions are as follows:
    What is the recommended configuration of RAID (Hardware)?
    What is the default set up of partitioning when installing sbs 2003?
    What is the recommended partinoning when installing sbs 2003?

    Any suggestions are welcome

    Thanks in Advance

    John Miele, May 19, 2006
    1. Advertisements

  2. SBS does not do any default partitioning, you decide :)

    I have seen folks suggest mirror os and raid 5 the data, not sure why.

    Many folks to suggest splitting exchange on diff platters for speed, but I
    doubt any SBS org will have that much email.

    I was just wondering about 2 sets of raid 5 but not sure if the 7th drive
    can be a hot spare for 2 sets?

    So I would put 6 in a raid 5 and have the hot spare. Dependeing on your
    email limits 75 gb :) 100gb on C: and make the rest a data partition

    SBS Rocks !!!
    Join the worlds largest SBS User Group
    Grey Lancaster SBS Rocks MVP], May 19, 2006
    1. Advertisements

  3. John Miele

    Mark Welte Guest

    Expanding on what Grey said if you decide not to use the 7th drive as a
    hot spare you can use it as a fourth drive in the last RAID array. The
    more drives a RAID has to use in a RAID 5 configuration the better. It
    gives you a little more performance and a little more redundancy. The
    parity stripe is now across 4 drives instead of three so you could
    theoretically loose 2 drives in that array and still rebuild. As an
    overview Raid 1 has good read and write performance. Raid 5 has great
    read performance with good write performance.

    One thing you might want to make sure that you do is double check the
    cache policy of the controller. Write-back gives some performance gains
    but unless you have a battery on the card itself it is better to use
    write-thru. This is especially important if the server is going to have
    SQL on it. I have read that SQL should be run with cache set to
    write-thru due to corruption issues.

    Mark Welte, May 19, 2006
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.