Re: Number of Spindles Exchange + SQL
- From: <workinghard@xxxxxxxxxxxxxx>
- Date: Wed, 13 Dec 2006 10:44:21 +0100
just some taughts and considerations four you ...
Maybe I should have said up front that I'm not going to run on RAID 5.
As for the physical infrastructure, all my drives will be Fibre Channel
on EMC Clariion.
Well, I did some rough math and saw that even if I have 30 users at
100% concurrency and 1 IOPS, I'm still way below the throughput of a
single RAID 1.
I'm still a little torn. Perhaps O/S+logs on one mirror, and a
combination of Exchange+SQL+Shared-Folders on another? Is there a
formula for sizing Exchange and SQL log partitions?
Judging from the fact that EMC/Fibre (allready have one in place that
you'll leverage?) is involved I'll asume that those 25
people will hit that system vigorously :-) and have mailboxes of
2 GB a person. I would start out with RAID 1's. With 25 users and mainly
exhange you will never exceed the IOPS capacity of RAID 1 for exchange,
really unless that company is a SPAM research business that will get/send
1000 of mails per hour :-) It is very hard to give you advice when we don't
know the I/O and other details. Depending on that infor your customers might
be well served with 2 or 3 mirrors on SAS disks versus using fibre disks.
Keep in mind that if one builds high performance/high available database
systems thos whitepapers make very valid statements. But you need to find
the correct performance, redundancy versus cost. For 25 users with out
knowing anything else I'd say starting out with 15.000 SAS Disks with a good
RAID Controller and adequate diskspace combined with a dual core CPU, 4 GB
RAM
and 1Gbps ethernet + switches will last you for 5+ years and beyond.
Als long as IO does not become a liùmiting factor adding disks only costs
moneywith no performance benefit. You do get more space :-)
The sizing of logs is dependent on amount of transactions: the more the
bigger the logs become. That does not mean you need a lot of space but that
you need to backup a lot wich clears the logs. It is prudent to have extra
space in case their is a backup issue (logs can than just keep growing until
you fix the issue) and in case you need to move all mailboxes to a new store
etc .. everything is logged and you need some overhead but don't go
overboard. Do you have any indications what the log volume is daily?
The same kind of reasoning goes for SQL Server logs.
Database: size for 110 % of the maximum database size(s). Which means that
if you have 3 data bases of 20 GB each you'll want around 130 GB. This
assures you'll have all the space you need to run every possible disaster
recovery scenario (eseutil, ...etc ...). Always make sure you have room (can
be external disk to male copies of the file before your work on them). When
sizing take into account mailbow growth.
.
- Follow-Ups:
- Re: Number of Spindles Exchange + SQL
- From: John White
- Re: Number of Spindles Exchange + SQL
- References:
- Re: Number of Spindles Exchange + SQL
- From: John White
- Re: Number of Spindles Exchange + SQL
- Prev by Date: RE: Double typing with RWW
- Next by Date: Exchange server-side rule?
- Previous by thread: Re: Number of Spindles Exchange + SQL
- Next by thread: Re: Number of Spindles Exchange + SQL
- Index(es):
Relevant Pages
|
Loading
