Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

At our office, we're in the planning stage for an Exchange 2010 setup. We're purchasing 4 server licenses and trying to set up a somewhat resilient Exchange infrastructure. I wanted to see if our current idea would work or not.

I'm not trying for a discussion or debate, so just a simple "Yes" or "No, there's a limitation that will keep X from working right" will work.

We're planning on putting this up alongside our current Exchange 2003 server and migrating current users over a few weeks time.

For two of the servers, we want to just install the Mailbox role and set them up to split the users into two databases operating in a DAG. So, there will be 1 active and 1 passive EDB per mailbox server.

For the other two servers, we want to set up Client Access Server and Hub Transport roles on each of them. Client Access Server will be load balanced through Windows native NLB (Network Load Balancing), and we will set up a script to remove a failing server from the NLB cluster in case application errors start. Hub Transport does not work with on-server load balancing, but we don't see much of a need for it since we can balance incoming mail through our dedicated Spam/AV appliance. Outgoing mail will be enabled on both Hub Transport servers.

Since we already have a spam/AV solution in our DMZ, we don't see much of a need for the Edge Transport role.

All four of these servers will be hosted on a fairly robust ESXi cluster, with separation of each pair enforced through vCenter.

So, are we missing something completely obvious here, or does this seem like a fairly decent single-site resiliency setup?

EDIT: I did some additional research since I was concerned about CAS and HT being on the same servers with NLB for CAS, since there is a lot of documentation saying that HT and NLB do not get along at all. It works as long as you only NLB ports 80 and 443, according to this thread on Technet: http://social.technet.microsoft.com/Forums/en-US/exchangesvravailabilityandisasterrecovery/thread/8f3074d6-7369-4e27-86d5-7884d726938e/

share|improve this question
    
Posting this a comment since I'm a bit unsure.. but isn't the edge transport role required in a Exchange organization? It's the SMTP stack.. How else are you going to relay mail to your mailwasher? –  pauska Mar 18 '11 at 14:15
    
You can receive SMTP directly on a hub transport server. Edge Transport is meant to be used as a "safe zone" in your DMZ for doing spam and AV filtering before it hits your internal network. –  Hyppy Mar 18 '11 at 14:16
    
Update: This setup worked out great. 2x CAS+HT, 2x Mailbox, with spam/av appliances replacing our need for an Edge Transport. All redundant; we can unplug any of our ESXi boxen and never see more than a second of availability loss. –  Hyppy May 11 '11 at 17:30

1 Answer 1

up vote 3 down vote accepted

Yes, it will work. I wouldn't call it optimal though. Beware running NLB in VMware, you need to do a few extra steps. How's that for no discussion/debate....

share|improve this answer
    
LOL Not trying to shut down answers, just want to avoid the "You're too open ended! I CLOSE THEE" responses from the mods. Thanks for the once-over though, I appreciate it. –  Hyppy Mar 18 '11 at 14:06
    
I looked up some VMware documentation about NLB in guest OSs. They have a fairly concise guide here: vmware.com/resources/techresources/1072 - Multicast NLB is already supported by my switch (Cisco 6509E), so according to the guide I'll want to do multicast which will likely require no further setup. –  Hyppy Mar 18 '11 at 14:26

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.