TechArena Community

TechArena Community (http://forums.techarena.in/)
-   Windows Software (http://forums.techarena.in/windows-software/)
-   -   Problem of Hub Transport server and Client Access in Exchange Server (http://forums.techarena.in/windows-software/1356825.htm)

Sheravat 09-08-2010 12:29 PM

Problem of Hub Transport server and Client Access in Exchange Server
 
Our organization currently has implemented Exchange 2007. We have a high availability solution consisting of four Exchange 2007 servers: two servers that have the roles of the Hub Transport server and Client Access installed, and two servers acting as nodes in the cluster mailbox server in a cluster Cluster Continuous Replication (CCR). Exchange 2007 servers that are installed roles Hub Transport server and client access are configured in a Windows NLB to load balance and provide automatic failover for inbound connections and SMTP client. This solution works well, but now that Exchange 2010 was released, we want to pass this version of the latest Exchange server. Not only are several new features that we want to use, but have also heard that we can reduce the amount of two Exchange servers without losing the functions of HA we already know. Are there special considerations we should take into account before moving to a HA Exchange solution consists of only two servers? Need your help desperately. :notworthy :notworthy

Pauline 09-08-2010 12:33 PM

Re: Problem of Hub Transport server and Client Access in Exchange Server
 
Yes, in order to create a messaging solution highly available Exchange 2007 Failover automatically and without any point of failure at the hardware or storage, needed a total of four teams: two servers with Transport server roles Hub and Client Access Exchange 2007 installed, and two that act as nodes in a cluster based on cluster continuous replication (CCR).

Dodge 09-08-2010 12:34 PM

Re: Problem of Hub Transport server and Client Access in Exchange Server
 
Transportation Hub has integrated load balancing and failover for communication within the site and you can do through redundant mechanisms DNS round robin. But as the role of the Client Access server does not include any load balancing feature, usually also had to configure the two machines as cluster nodes in a network load balancing Windows (WNLB) to provide load balancing and switching for automatic error for incoming connections from clients and servers on the Internet and other external networks.

BlackSunReyes 09-08-2010 12:34 PM

Re: Problem of Hub Transport server and Client Access in Exchange Server
 
Quote:

Our organization currently has implemented Exchange 2007. We have a high availability solution consisting of four Exchange 2007 servers: two servers that have the roles of the Hub Transport server and Client Access installed, and two servers acting as nodes in the cluster mailbox server in a cluster Cluster Continuous Replication (CCR).
The two machines that act as cluster nodes in the cluster had the CCR Mailbox server roles installed assets and liabilities respectively, so that the clustered mailbox server (CMS) could change or fail over to either nodes. Finally, one of the dedicated front-end servers as a witness of the share (third vote) in the CCR cluster.

Janet J 09-08-2010 12:35 PM

Re: Problem of Hub Transport server and Client Access in Exchange Server
 
As you almost certainly know, CCR (and SCC, LCR and SCR in this case) has been detached from Exchange 2010. Instead, Exchange 2010 commences an innovative feature called Groups of availability database (DAG). This characteristic uses the same synchronization technology combined CCR and SCR, but it has many new-fangled features and many other features that are significantly better than CCR and SCR. An appealing aspect is that Exchange 2010 is compatible with other Exchange 2010 roles (Hub Transport, Client Access, and even unified messaging) installed on the identical server which has a Mailbox server role has been added to a DAG. This means you no longer need to spend two machines as servers for front-end server roles Hub Transport and Client Access. Just install all the Exchange 2010 roles mandatory in the two machines and smart, has a messaging solution based on Exchange 2010 fully redundant. :thumbup1:

Samra 09-08-2010 12:39 PM

Re: Problem of Hub Transport server and Client Access in Exchange Server
 
Well, see, like using the component DAG Failover Cluster Windows (WFC) to some scope (mainly heartbeat and cluster database), you cannot constitute the two servers as nodes in a Windows NLB and that does not sustain the use of both WFC and WNLB on the identical server. This has not been supported since Windows NT 4.0 and is due to potential divergences of hardware sharing between the Cluster service and WNLB.

DANIEL 602 08-10-2010 06:29 AM

Re: Problem of Hub Transport server and Client Access in Exchange Server
 
Although still using WFC and although DAG is a feature of Enterprise Edition, do not really need Exchange 2010 Enterprise Edition to use DAG. Unlike Exchange 2007 CCR, DAG is also included with the Standard Edition of Exchange 2010. But keep in mind that is limited to a total of five databases (including copies of data base of active and passive) in this scenario.

Chakradev 16-02-2011 08:14 PM

Re: Problem of Hub Transport server and Client Access in Exchange Server
 
As you install the CAS and HT roles on the equivalent machine as the Mailbox server role and is a DAG member server, you can save two machines and two licenses for Windows 2008 Standard Edition and Exchange 2010. If does not have a peripheral load balancer in your environment, you can use a virtual load balancer device or buy a load balancer based on hardware. Certainly, you need a server acting as a witness server as well, but although it is a recommended practice, it need not essentially be an Exchange server. It could be some file server in Windows 2003/2008 environment.


All times are GMT +5.5. The time now is 10:28 AM.