Exchange Server - recommended disk configuration?
Asked By Kremlar
19-Nov-09 10:43 AM
We're currently putting together a new server to host Exchange for
organization, about 50 users.
We're using a chassis that supports up to 6 drives, using a decent SAS/SATA
RAID card with battery backup.
Our budget will not allow for 15K RPM SAS drives, so we are looking at 10K SATA
drives. Wondering how best to use our 6 available drive bays to get optimal
Exchange performance.
Should we go with:
2 drives in a RAID1 configuration
+3 drives in a RAID5 configuration
+hotspare
or
5 drives in a RAID6 configuration
+hotspare
My understanding is that Exchange performs better with 2 physical arrays
versus a single array with multiple partitions.
Any advice?
Friday
(1)
Databases
(1)
Spindles
(1)
Hotspare
(1)
Battery
(1)
Volumes
(1)
Chassis
(1)
Spares
(1)
Ed Crowley [MVP] replied to Kremlar
Let's assume you are asking about Exchange 2007 since you did not say.
However, my answer pretty much applies to any version.
If you are limited to six drives, I would go with:
2 drives in RAID-1, partititioned into two, one for OS + Swap File and the
other for Exchange logs
4 drives in RAID-1 or RAID-5 for the databases
and skip the hot spare, maybe buying an additional cold spare if your
service contract does not provide for fast replacement.
The reason behind two arrays is not so much performance as recoverability,
especially with just 50 users. You want to keep the logs and databases on
separate physical volumes so that if you lose either one, after recovering
you can still get all your data back up to the point of failure.
--
Ed Crowley MVP
.
Kremlar replied to Ed Crowley [MVP]
Hi Ed -
Thanks for your reply. Yes, 2007. Since performance is not so much an issue
with 50 users, any reason why you would recommend against a 3-drive RAID5
leaving the 6th drive as a hotspare?
Replacement of a dead drive would be fairly quick, but my nightmare scenario
is a disk failure on a Friday evening that is not attended to until the
following Monday. A hotspare would make me feel better.
Ed Crowley [MVP] replied to Kremlar
With so few drives the hot spare would be a waste, in my opinion. You
already have hot spares in both RAID configurations. Instead put the drive
in service and give people bigger mailbox quotas. Get a monitoring system
that pages you when your disks die.
--
Ed Crowley MVP
.
f825_633 replied to Kremlar
I would not and we do not bother with 'hot' spares, they are
spindles are running and burning their life away just as
much as the drives they are supposed to be backing up.
Have a spare or two sitting on a shelf ready to be pressed
into service, your raid is fault tolerant anyway - that is
you can drop a single drive without losing the system, just
replace the dead drive when it fails and if remainder drives
are near to the MTBF replace them all one by one rebuilding
the raid as you go.
and as other have suggested, make sure or get the raid
monitoring software for your system,
- and implement a backup system for your data - do not rely
on the raid - you never know.....
good luck...

7 days deleted items retention. As you migrate to MAPI clients, the size of the databases will grow as more mail is retained on the server, however the change deltas will a separate server at 10 minutes intervals. Individual Logs gather data Monday 0:00 to Friday 23:59 for each EVS01, EVS02, EVS03, and EVS04 for a weekly period excluding weekends has 4 mailbox stores. I finally made them move each set of 4 mailbox store databases within each Storage Group to a dedicated drive letter. When they setup the existing 20 from which you are collecting data has a bottleneck and you'll need to add spindles to correct the problem. Every storage vendor has a plot for drives of different types example, I get 130 IOPS at 20ms and over 200 IOPS at 60ms. When the spindles get overloaded to a point (about 400 IOPS for our example 15K FC spindle) the example, I get 130 IOPS at 20ms and over 200 IOPS at 60ms. When the spindles get overloaded to a point (about 400 IOPS for our example 15K FC spindle) the are you getting this information from? 20ms and over 200 IOPS at 60ms. When the spindles get overloaded to a point (about 400 IOPS for our example 15K FC spindle) the are you getting this information from? 20ms and over 200 IOPS at 60ms. When the spindles get overloaded to a point (about 400 IOPS for our example 15K FC spindle) the
disk and user? Exchange Server What figures is everyone working off when sizing quantity of spindles for Exchange 2003 databases please? Let's assume RAID10 and brand new 15k SAS spindles. The average IOPs per spindle seem to vary wildly from results in Google as do in advance. Exchange Admin Discussions Outlook (1) IOPs (1) Max (1) Avg (1) B957327604c6 (1) Databases (1) C6084d20 (1) Spindles (1) To get the IOPS requirement, you'd need to know something about the user every ten seconds and includes three full exchange aware backups from / to the same physical spindles (a RAID10 with 2 partitions). My interpretation is that other than the odd spike, the that if I wanted to keep my stores at around 100gb then 4x300gb 15k SAS spindles should offer sufficient IOPs even assuming an average of 1 IOPS per user which seems per, disk, and, user? description: What figures is everyone working off when sizing quantity of spindles for Exchange 2003 databases please Let's assume RAID10 and brand new 15k SAS spind
How to move 4 exchange 2007 databases into their own Storage group Exchange Server Folks We have five databases in the same (First) storage group. (I believe five databases are the maximum allowed but you are allowed 50 storage groups with the 2007 Enterprise edition). We want to create a total of 5 storage groups and move 4 databases into their own Storage group ending up with one database in each storage group. This point the users to their new database location. keywords: How, to, move, 4, exchange, 2007, databases, into, their, own, Storage, group description: Folks We have five databases in the same (First) storage group. (I believe five databases are the maximum allowed but you are allowed 50 storage group
database question Exchange Server Exchange server 2003 Standar acepts only 1 data store and 2 databases. Are 2 databases include Public database? MC Exchange Setup Discussions Exchange Server (1) Database (1) MSFTNGP (1) Outlook accessed by using MAPI and Outlook Web Access Up to four more public folder store databases that are accessible only programmatically http: / / support.microsoft.com / kb / 822440 - - Bharat Suneja MVP - Exchange Standard, database, question description: Exchange server 2003 Standar acepts only 1 data store and 2 databases. Are 2 databases include Public database MC?