I'm trying to get a handle on the top level design for a new Exchange 2010 environment.
I'm looking for as much business continuity (redundancy) as possible.
My idea was to have a four server setup in production and two servers in DR as follows:
2 x TMG (Threat Management Gateway) to load-balance clients between the back-end servers.
2 x CAS/HUB/DAG servers, these two machines would handle all Exchange functionality with DAG split across each so in the event one failed the second would take the reigns.
DR would be a replica but with 1 of each. Manual failover of the DAG for DR.
My question is, can the CAS be run on the HUB and Database server in this scenario or do you have to separate the CAS out (to load balance for failover) on to its own two servers sandwiched between the TMG and Dbases?
For reference: The spec of the back-end servers are 24 core (2x 12core AMD 2.2GHz), 32GB ram, 10TB SAS storage. Pretty solid boxes more than capable of handling the workload. The TMG would just be an entry level 1U ‘web’ server or VM boxes as they only do pass-through and load-balance clients.
I'm looking for as much business continuity (redundancy) as possible.
My idea was to have a four server setup in production and two servers in DR as follows:
2 x TMG (Threat Management Gateway) to load-balance clients between the back-end servers.
2 x CAS/HUB/DAG servers, these two machines would handle all Exchange functionality with DAG split across each so in the event one failed the second would take the reigns.
DR would be a replica but with 1 of each. Manual failover of the DAG for DR.
My question is, can the CAS be run on the HUB and Database server in this scenario or do you have to separate the CAS out (to load balance for failover) on to its own two servers sandwiched between the TMG and Dbases?
For reference: The spec of the back-end servers are 24 core (2x 12core AMD 2.2GHz), 32GB ram, 10TB SAS storage. Pretty solid boxes more than capable of handling the workload. The TMG would just be an entry level 1U ‘web’ server or VM boxes as they only do pass-through and load-balance clients.
