<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Exchange Server Front End</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/exchange-server-front-end/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/exchange-server-front-end/</link>
	<description></description>
	<lastBuildDate>Tue, 18 Jun 2013 06:31:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: saturno</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/exchange-server-front-end/#comment-86584</link>
		<dc:creator>saturno</dc:creator>
		<pubDate>Sat, 15 Jan 2011 16:54:39 +0000</pubDate>
		<guid isPermaLink="false">#comment-86584</guid>
		<description><![CDATA[Hi Poweruser,

In a common scenario, you have two ways to load balance MS Exchange FE:
1 - DNS with Round Robin;
2 - Network load balancing.

The DNS RR approach is the easiest and cheapest way to load balance a web server (Exchange FE).
Configuring Round Robin in DNS is as simple as assigning multiple (in this case 2) ip addresses to a unic Fully Qualified Domain Name.
In this case the balancing is done by the DNS server which will answer every request with a different IP address.
This solution only requires you to configure your DNS infrastructure to be able to load balance those Exchange FE.

If you want/need a more robust solution than go for Network Load Balancing.
For NLB you need an additional network card in each server and to configure NLB. NLB is a Windows server 2k3 and over service that monitor the availability and load to distribute the load over each node of the cluster.

For a more in depth and detailed instruction on both scenarios please read &lt;a href=&quot;http://www.msexchange.org/tutorials/Load-Balancing-Exchange-Front-End-Servers.html&quot;&gt;this article&lt;/a&gt;.

Regards,]]></description>
		<content:encoded><![CDATA[<p>Hi Poweruser,</p>
<p>In a common scenario, you have two ways to load balance MS Exchange FE:<br />
1 &#8211; DNS with Round Robin;<br />
2 &#8211; Network load balancing.</p>
<p>The DNS RR approach is the easiest and cheapest way to load balance a web server (Exchange FE).<br />
Configuring Round Robin in DNS is as simple as assigning multiple (in this case 2) ip addresses to a unic Fully Qualified Domain Name.<br />
In this case the balancing is done by the DNS server which will answer every request with a different IP address.<br />
This solution only requires you to configure your DNS infrastructure to be able to load balance those Exchange FE.</p>
<p>If you want/need a more robust solution than go for Network Load Balancing.<br />
For NLB you need an additional network card in each server and to configure NLB. NLB is a Windows server 2k3 and over service that monitor the availability and load to distribute the load over each node of the cluster.</p>
<p>For a more in depth and detailed instruction on both scenarios please read <a href="http://www.msexchange.org/tutorials/Load-Balancing-Exchange-Front-End-Servers.html">this article</a>.</p>
<p>Regards,</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 3/10 queries in 0.037 seconds using memcached
Object Caching 267/273 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-06-18 06:46:00 -->