Scenario:
Small company, 2 geographic sites connected by 20Gbps Fiber link, single AD Site, Exchange 2003 (500 mailboxes one site, 300 the other). Virtual Infrastructure exists at both geographic sites.
Mailbox users are site-specific and in current Exchange 2003 solution, have mailbox servers located at each site respectively.
Requirements:
To upgrade to Exchange 2010 as first phase upgrade.
To maintain mailbox site affinity for users located at each site, so that power-outages only affect mailbox users at that site.
Minimise costs and server count where possible, whilst providing higher availability for maintenance work to be peformed during normal working hours for the 2010 solution.
No requirement for DR copies of mailboxes between the sites.
Constraints:
Power outages at each physical location occur multiple times per year, quite frequently for more than the run-time of the UPS kit in place, so there is the real potential for ALL kit to go down at either of the sites, as has done to date.
Question:
What is the most appropriate DAG design?
Initial Thoughts:
Geo-site A: 2 x Mailbox nodes + 1 x CAS/HT node (FSW for DAGA)
Geo-site B: 2 x Mailbox nodes + 1 x CAS/HT node (FSW for DAGB)
A total of 6 servers required, which may seem overkill. However, CAS/HT nodes can be load-balanced using NLB between well-connected geo-sites A and B via 20Gbps resilient Fiber (Hard to justify cost of VLB or HLB for such a small number of users).
This provides local HA against single server failure for both DAGs at either site. If one site goes off-line due to power-outage, entire DAG and NLB node at remaining site continues to service clients.
Is there a simpler model that would work well whilst providing high availability for each geo-site, bearing in mind the possibility of complete power outage at each site?
Thanks in advance for ideas / thoughts.
MSEBlogger (Technet)