Exchange: System design
'lo guys :)
I'd like to run my e-mail system proposal past anyone who is paying attention since I only get to do this once every 2 / 3 years ;)
Initially a 250 user system with scope to expand to 500+. Includes HA because people get really really upset when it isn't around. This is a heavy system, but there we go, full fault tolerance is a project requirement.
Mailbox Servers (* 2):
Windows 2008 R2 Enterprise
Exchange 2010 Standard
RAM: 16Gb (minimum recommended by MS spreadsheet thing is 12Gb based on 200 messages per user per day)
CPU: 1 * Quad-core Xeon
Disk (FC SAN - 10k SAS):
4 * 100Gb for databases (RAID 1+0)
4 * 20Gb for Logs (RAID 1+0)
Mailbox HA:
4 databases in a single DAG. 2 active / 2 passive databases per server in normal operation
Client Access / Hub Transport (* 2):
Windows 2008 R2 Standard
Exchange 2010 Standard
RAM: 8Gb
CPU: 1 * Quad-core Xeon
Disk: 1 or 2 local mirrored pair (anything goes)
I kind of want the Personal Archive thing. Alas more stores is going to need an upgrade to Exchange 2010 Enterprise (I really don't want to have 200Gb+ stores) as well as the Enterprise CALs. If that goes in we're likely to allocate up to 2Tb per server of (FC SAN based) 7200 SATA disk (probably split over another 4 stores in the same manner as the regular stores), in addition to the disk layout above.
Ideally the two CAS servers will be configured as an Array (hopefully using MS NLB). The two HT servers will be accepting inbound mail from the anti-spam system or by MX, no NLB for the HT. I'm hoping these roles can be combined like this!
All servers will be on the same AD site, serviced by 2 or 3 DC \ GCs.
Missing anything?
Cheers!
Chris
I'd like to run my e-mail system proposal past anyone who is paying attention since I only get to do this once every 2 / 3 years ;)
Initially a 250 user system with scope to expand to 500+. Includes HA because people get really really upset when it isn't around. This is a heavy system, but there we go, full fault tolerance is a project requirement.
Mailbox Servers (* 2):
Windows 2008 R2 Enterprise
Exchange 2010 Standard
RAM: 16Gb (minimum recommended by MS spreadsheet thing is 12Gb based on 200 messages per user per day)
CPU: 1 * Quad-core Xeon
Disk (FC SAN - 10k SAS):
4 * 100Gb for databases (RAID 1+0)
4 * 20Gb for Logs (RAID 1+0)
Mailbox HA:
4 databases in a single DAG. 2 active / 2 passive databases per server in normal operation
Client Access / Hub Transport (* 2):
Windows 2008 R2 Standard
Exchange 2010 Standard
RAM: 8Gb
CPU: 1 * Quad-core Xeon
Disk: 1 or 2 local mirrored pair (anything goes)
I kind of want the Personal Archive thing. Alas more stores is going to need an upgrade to Exchange 2010 Enterprise (I really don't want to have 200Gb+ stores) as well as the Enterprise CALs. If that goes in we're likely to allocate up to 2Tb per server of (FC SAN based) 7200 SATA disk (probably split over another 4 stores in the same manner as the regular stores), in addition to the disk layout above.
Ideally the two CAS servers will be configured as an Array (hopefully using MS NLB). The two HT servers will be accepting inbound mail from the anti-spam system or by MX, no NLB for the HT. I'm hoping these roles can be combined like this!
All servers will be on the same AD site, serviced by 2 or 3 DC \ GCs.
Missing anything?
Cheers!
Chris
ASKER
I was hoping for some feedback on the proposal rather than links to other versions of instructions (since that's the kind of thing I've spent today going through). Have you actually set a system similar to this up? What did you do? Are there any gotchas with this design that might incur an unexpected cost?
Cheers,
Chris
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Cool, thanks :)
We use MessageLabs to filter inbound mail (anti-spam / anti-virus). The two HTs won't be recieving directly although they will be set up in such a way that they can if absolutely necessary. That is, they will have appropriate public DNS names, PTR records, and certificates but won't permit direct inbound connections by default (except from MessageLabs).
I won't get away with incorporating an Edge Server (or two) into the design as long as we're paying for that lot to be done elsewhere.
Chris
Looks well planned, you got failover, redudancy, your spam and anti-virus figured out, dns records, mx records, you seem to have to a good understand regarding the technical details, so for the exchange infrastructure design it looks good to me.
Feel free to ask any more questions if you need assistance!
Feel free to ask any more questions if you need assistance!
ASKER
Thanks!
-If will include SP1 onto your excahnge servers will you get the archiving option as well
-You will need to set up dag with the two exchange servers withholding the mailbox role.
Since you mentioned that people get upset regarding HA when it isnt around I suggest you read the answeres provided here:
https://www.experts-exchange.com/questions/26537405/setting-up-a-DAG-without-a-secondary-subnet.html
-You will need to use WNLB with the two exchange servers withholding hub / cas
Further information you can see options and command outlets for this architechture design in:
https://www.experts-exchange.com/questions/26504284/DAG-on-Exchange2010.html
also two good guides below:
http://www.shudnow.net/2009/10/29/exchange-2010-rtm-dag-using-server-2008-r2-%E2%80%93-part-1/
http://blogs.microsoft.co.il/blogs/eldadc/archive/2010/04/14/how-to-configure-exchange-2010-disaster-recovery-site-using-dag.aspx
And last remember you to order correct certificates,
feel free to ask any questions, hopefully I can assist in answering them,
cheers