Exchange 2010 File Share Witness design, 2 sites
Posted on 2011-03-17
I am currently performing a transition from Exchange 2003 to 2010, and so far so good.
I have now come to the point where I need to start building the resilience into the new system to allow for system failures.
We are located in site A. site B is the datacentre, and all exchange kit and DCs are located there.
I wanted to build (presumably) a DAG with 2 servers at the DC, so in case 1 fails, the other will take over with a live up to date copy of the database. Can I build an Exchange server at our office (Site A) as the copy and if the link to the DC goes the local server kicks in?
The issue here is the FSW. In both scenarios above, if I have the FSW at the DC then how will the local server at site A kick in? Or shall I put the FSW at site A instead, so if the link to the DC is lost, the local exchange server kicks in?
I assume the exchange mailbox servers can replicate all database traffic between them and stay synchronised and up to date in case the non-master has to assume control?
Our CAS servers are at the DC (site B).
Any help would be appreciated!