How to make a dicision to adoption Of NLB or Hardware LoadBalancing
I wonder whether adopting the NLB or HardwareLoadBalancing to CAS server and HUB server?
Does anyone have some answer or advice?
Is there the decision making Process?
I found the similar quetion about HLB below. But it's about HLB recommendation.
I want to know the difference about NLB and HLB. For perfomance, protocol monitoring etc...
And Microsoft have some recommendations?Best Regards.
Answers
You can make use of NLB except for the following situations:
- When you have more than 8 nodes to balance, because the broadcasts will slow performance significantly.
- When the server is a member of a mailbox DAG, because NLB and Clustering will not install on the same box.
Ideally an HLB is typically preferred as you will always gain improved performance, but it is ultimately a question of cost and scale that will determine which LB you choose.
Sean | http://seanv.wordpress.com- Marked As Answer byhokkaikan Tuesday, November 17, 2009 5:50 AM
- Proposed As Answer bySean van Osnabrugge Saturday, November 07, 2009 12:46 AM
- I am not aware of a Load Balancing appliance that will monitor MAPI connections. Typically it is PING or HTTP. I recall some devices are able to install probes on a server to montitor CPU/Memory performance and determine a path based on the load of the server but I ahve never used them. I think they are expensive.
In Exchange 2010 DR has gotten much better by using DAG. The trick is if you do lose a site you will have to manually change some DNS entries to point ppl to the DR site. You can use different MX records for your mail routing. If Site 1 is down have a MX record of maybe 50 pointing to DR. Keep in mind though spammers will target a higher MX record so have some good anti-spam devices on your DR side.
OWA will be a trick as well as OLA if you use that. But mail routing won't be a problem with redundant MX records so the mail will be waiting for your users when they get there. :)
SF - MCITP:EMA, MCTS: MOSS 2007, OCS 2007, Exchange 2007 -- http://www.scottfeltmann.com- Marked As Answer byhokkaikan Tuesday, November 17, 2009 5:51 AM
All Replies
You can make use of NLB except for the following situations:
- When you have more than 8 nodes to balance, because the broadcasts will slow performance significantly.
- When the server is a member of a mailbox DAG, because NLB and Clustering will not install on the same box.
Ideally an HLB is typically preferred as you will always gain improved performance, but it is ultimately a question of cost and scale that will determine which LB you choose.
Sean | http://seanv.wordpress.com- Marked As Answer byhokkaikan Tuesday, November 17, 2009 5:50 AM
- Proposed As Answer bySean van Osnabrugge Saturday, November 07, 2009 12:46 AM
Depending on the size of your organization will determine how you NLB and your budget.
I see more and more referernces going to a HW NLB appliance in the mix because of improved performance etc.
SF - MCITP:EMA, MCTS: MOSS 2007, OCS 2007, Exchange 2007 -- http://www.scottfeltmann.com- Hi, Sean van Osanabrugge & Scott Felman
Thank you for your help.
I understood.
And I'm aware of the process monitoring.
It's my understanding that
・If NLB, Exchange process monitoring is only the "PING" monitoring of the Server.
・If HLB, Exchange process monitoring is "PING" and "HTTP" monitoring of the Server.
Is it correct?
And
Except of "PING" and "MAPI" monitoring is possible?
And my understanding,
ＮＬＢ＆ HLB adoption is also cutted by Disaster Recovery System Requirement.
Thank you - I am not aware of a Load Balancing appliance that will monitor MAPI connections. Typically it is PING or HTTP. I recall some devices are able to install probes on a server to montitor CPU/Memory performance and determine a path based on the load of the server but I ahve never used them. I think they are expensive.
In Exchange 2010 DR has gotten much better by using DAG. The trick is if you do lose a site you will have to manually change some DNS entries to point ppl to the DR site. You can use different MX records for your mail routing. If Site 1 is down have a MX record of maybe 50 pointing to DR. Keep in mind though spammers will target a higher MX record so have some good anti-spam devices on your DR side.
OWA will be a trick as well as OLA if you use that. But mail routing won't be a problem with redundant MX records so the mail will be waiting for your users when they get there. :)
SF - MCITP:EMA, MCTS: MOSS 2007, OCS 2007, Exchange 2007 -- http://www.scottfeltmann.com- Marked As Answer byhokkaikan Tuesday, November 17, 2009 5:51 AM
