Chinaunix首页 | 论坛 | 博客
  • 博客访问: 856231
  • 博文数量: 436
  • 博客积分: 0
  • 博客等级: 民兵
  • 技术积分: -103
  • 用 户 组: 普通用户
  • 注册时间: 2016-08-01 09:48
个人简介

爱生活,爱IT

文章分类

全部博文(436)

文章存档

2015年(1)

2014年(2)

2013年(6)

2011年(39)

2010年(176)

2009年(30)

2008年(28)

2007年(54)

2006年(91)

2005年(9)

分类:

2010-06-13 13:47:20

全文请阅,请点击:
Exchange Server 2010 CAS Array, 是Exchange高可用性配置不可少的之应用。通过配置多台CAS,借助于NLB,配置成CAS 阵列,可以规避客户端访问失败风险。

As mentioned in my previous blog post about the Exchange 2010 RPC Client Access Service and the ClientAccessArray, Exchange’s dependence on the Client Access Server (CAS) role has increased dramatically in Exchange 2010.  This is because, in Exchange 2010, on-network Outlook MAPI connectivity now connects to a mailbox through the CAS role via the RPC Client Access Service.  As a result, high availability of the CAS role is crucial since any failure of CAS could affect Outlook client connectivity.  For smaller implementations or those where the limitations of native Windows Network Load Balancing (NLB) are not a major problem (please see my previous blog post for more information), NLB can work well.  The process for configuring NLB is fairly straightforward and I’ve outlined the steps below.

 
全文请阅,请点击:
阅读(3034) | 评论(0) | 转发(0) |
给主人留下些什么吧!~~