Exchange Daily Administration Seven: Client Access server high-availability deployment

Exchange Daily Administration Seven: Client Access server high-availability deployment

We have successfully deployed two Exchange2010 Cas/hub servers in the previous blog post, and now we are merging the two Cas/hub servers into a single CAS array. In Exchange2003, users have direct access to Exchange Mailbox servers. However, starting from Exchange2007, users will not be able to access the mailbox server directly, users who want to access the mailbox server must access the CAS server to connect to their own mailbox. This makes the CAS server a front-desk reception that must be faced to access the Exchange server. So once a problem occurs with the CAS server, the user accesses the Exchange server and comes into trouble immediately. To avoid this scenario, the more effective means is to put multiple CAS servers into a CAS array, so that can load balance and fault-tolerant role.

We want to configure Network Load Balancing on two Cas/hub servers. Network Load Balancing (NLB) is no stranger to many friends. NLB needs to pass the heartbeat between the hosts via the heartbeat card, so if we need to use two NICs on the Cas/hub server, we need to consider several scenarios:

1, using two network card: A network card to pass the heartbeat signal, a network card for the production environment.

2, using a network card: A network card body and two jobs is also possible (considering the heartbeat signal data volume is not large).

In this experiment we use a NIC.

Create a Network Load Balancing cluster (NLB)detect if a Network Load Balancing cluster is installed

Open Server Manager---Click Features:

650) this.width=650; "height=" 342 "title=" clip_image002 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image002 "src=" http://s3.51cto.com/wyfs02/M00/6E/C9/ Wkiol1witqfqdvz3aae1hrzrat0723.jpg "border=" 0 "/>

OK, here you can see that we have installed the failover cluster, and if there are no friends installed, you can install it in the Add Features page.

Create a load-balanced cluster

Press the WIN+R key at the same time on the Cas/hub server:

650) this.width=650; "height=" 458 "title=" clip_image003 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image003 "src=" http://s3.51cto.com/wyfs02/M01/6E/C9/ Wkiol1witqfxfq2baagnnbqfka8649.jpg "border=" 0 "/>

Enter Nlbmgr Click OK:

650) this.width=650; "height=" 433 "title=" clip_image005 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image005 "src=" http://s3.51cto.com/wyfs02/M02/6E/C9/ Wkiol1witqewp-7_aafh9ltfkba673.jpg "border=" 0 "/>

Click Cluster---NEW:

650) this.width=650; "height=" 484 "title=" clip_image006 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image006 "src=" http://s3.51cto.com/wyfs02/M00/6E/C9/ Wkiol1witqeiekuaaaezqru5nzw942.jpg "border=" 0 "/>

Enter the host name of our Cas/hub server in the host location and click on the link:

650) this.width=650; "height=" 484 "title=" clip_image007 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image007 "src=" http://s3.51cto.com/wyfs02/M00/6E/CD/ Wkiom1wis0_xt0bcaafckk-qjl8832.jpg "border=" 0 "/>

The link status shows that all of our current IP addresses are listed below, and here we click Next:

650) this.width=650; "height=" 484 "title=" clip_image008 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image008 "src=" http://s3.51cto.com/wyfs02/M01/6E/CD/ Wkiom1wis0-ggslfaagkhh_o_ta034.jpg "border=" 0 "/>

Here we determine the priority, IP address, and initial host status without problems after clicking Next:

Note: Because the CASHUB1 server is the first server in the cluster, the priority is 1 by default

650) this.width=650; "height=" 484 "title=" clip_image009 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image009 "src=" http://s3.51cto.com/wyfs02/M02/6E/CD/ Wkiom1wis0_swnp6aaevu9s9jog590.jpg "border=" 0 "/>

Here we click Add to add the IP address of a cluster (because my cas-1 and cas-2 use the IP address respectively asked 192.168.2.3 and 192.168.2.4 so we use 192.168.2.100 in this cluster IP address):

650) this.width=650; "height=" 484 "title=" clip_image010 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image010 "src=" http://s3.51cto.com/wyfs02/M00/6E/CD/ Wkiom1wis1dhtdvtaahz5rcpk68087.jpg "border=" 0 "/>

Enter our cluster IP address and click OK later:

650) this.width=650; "height=" 484 "title=" clip_image011 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image011 "src=" http://s3.51cto.com/wyfs02/M01/6E/CD/ Wkiom1wis1dydkvkaafpy1k1fb0614.jpg "border=" 0 "/>

Make sure our cluster IP address does not have a problem after clicking Next:

650) this.width=650; "height=" 484 "title=" clip_image012 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image012 "src=" http://s3.51cto.com/wyfs02/M02/6E/CD/ Wkiom1wis1dqhomsaae_ye7-0ag142.jpg "border=" 0 "/>

Virtual IP settings for the cluster-after completion, we also set the domain name of the cluster, which should be the domain name used by this mail system on the public network. Here we enter the fully qualified domain name mail.contoso.com, click Next:

Note: After setting up the cluster domain name, we need to modify the mail.contoso.com corresponding IP in the DNS server to be the virtual IP of the cluster.

650) this.width=650; "height=" 484 "title=" clip_image013 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image013 "src=" http://s3.51cto.com/wyfs02/M00/6E/CD/ Wkiom1wis1dg0cxfaahen0b3mki220.jpg "border=" 0 "/>

Keep the port intact and click Done:

650) this.width=650; "height=" 331 "title=" clip_image015 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image015 "src=" http://s3.51cto.com/wyfs02/M01/6E/CD/ Wkiom1wis1dasihhaagq9sro-nu077.jpg "border=" 0 "/>

Click Finish to see the NLB cluster we just created

Cas-1 is the first host in the cluster, we will join the second host cas-2 to the cluster:

In Network Load Balancing Manager, the right mouse button mail.contoso.com:

650) this.width=650; "height=" "title=" clip_image017 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image017 "src=" http://s3.51cto.com/wyfs02/M02/6E/C9/ Wkiol1witqiqejknaaghcymlzv0230.jpg "border=" 0 "/>

Click Add Host to cluster:

650) this.width=650; "height=" 484 "title=" clip_image018 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image018 "src=" http://s3.51cto.com/wyfs02/M00/6E/C9/ Wkiol1witqmxazyxaaehzmpghem492.jpg "border=" 0 "/>

Enter our second host name cas-2, click Connect:

650) this.width=650; "height=" 484 "title=" clip_image019 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image019 "src=" http://s3.51cto.com/wyfs02/M01/6E/C9/ Wkiol1witqmsfr-naafcxxa4rjs784.jpg "border=" 0 "/>

You can see that you have successfully connected to our second host cas-2 and have obtained its IP address, here we click Next:

650) this.width=650; "height=" 484 "title=" clip_image020 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image020 "src=" http://s3.51cto.com/wyfs02/M02/6E/CA/ Wkiol1witqnihukmaagozqhj52k172.jpg "border=" 0 "/>

This determines that its priority is 2, that there is no error in the IP address, and that the initial host status is started after clicking Next:

650) this.width=650; "height=" 484 "title=" clip_image021 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image021 "src=" http://s3.51cto.com/wyfs02/M00/6E/CA/ Wkiol1witqnz18dcaagukquykx0897.jpg "border=" 0 "/>

As before, here we do not make changes to the port, click Finish:

650) this.width=650; "height=" 294 "title=" clip_image023 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image023 "src=" http://s3.51cto.com/wyfs02/M01/6E/CA/ Wkiol1witqmh5hcraafebwihsj8483.jpg "border=" 0 "/>

OK, the two NICs in the cluster have been aggregated successfully and the cluster status is normal.

Modify DNS Records

After creating a load-balanced cluster, we have the equivalent of having a virtual Cashub server, the IP of which is 192.168.2.100, and the domain name is mail.contoso.com. Next we want to modify the DNS record, the mail.contoso.com domain name of the intranet point to 192.168.2.100.

Open DNS Manager:

650) this.width=650; "height=" 377 "title=" clip_image025 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image025 "src=" http://s3.51cto.com/wyfs02/M02/6E/CD/ Wkiom1wis1gxqc_kaagaw0xluuy656.jpg "border=" 0 "/>

right mouse button mail this record:

650) this.width=650; "height=" 359 "title=" clip_image027 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image027 "src=" http://s3.51cto.com/wyfs02/M02/6E/CD/ Wkiom1wis1hiy09laagtn-dvtbq034.jpg "border=" 0 "/>

Click Properties:

650) this.width=650; "height=" 484 "title=" clip_image028 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image028 "src=" http://s3.51cto.com/wyfs02/M00/6E/CD/ Wkiom1wis1ljkne6aaep3kdqo-y114.jpg "border=" 0 "/>

To modify the IP address to the IP address of our cluster, click OK:

650) this.width=650; "height=" 362 "title=" clip_image030 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image030 "src=" http://s3.51cto.com/wyfs02/M01/6E/CD/ Wkiom1wis1lwakgsaagi_qrvxh8052.jpg "border=" 0 "/>

OK, you can see that the IP address has been modified successfully.

create a CAS array

Finally, we need to create a CAS array, in fact, let the EXCHANGE2010 server support load balancing. We open the Exchange Management Shell (EMS) on the CASHUB1 server:

650) this.width=650; "height=" 389 "title=" clip_image032 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image032 "src=" http://s3.51cto.com/wyfs02/M00/6E/CD/ Wkiom1wis1kwidwxaaho0swpmru503.jpg "border=" 0 "/>

Run "New-clientaccessarray-fqdn mail.contoso.com-name casarray.contoso.com-site Contoso". Note: Here mail.contoso.com is the fully qualified domain name of the Exchange Server CAs array, CASarray.contoso.com is the array name of the CAS array, and Contoso is the site name of Active Directory.

650) this.width=650; "height=" 369 "title=" clip_image034 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image034 "src=" http://s3.51cto.com/wyfs02/M02/6E/CD/ Wkiom1wis1ldhyhnaagzbswk7ku810.jpg "border=" 0 "/>

OK, CAS array creation complete.

After the CAS array is created, the two Cas/hub servers become the communications hub for the Exchange server. All communications for Exchange need to go through the Cas/hub server first.

This article from "Mr, Wu's Microsoft Blog" blog, reproduced please contact the author!

Exchange Daily Administration Seven: Client Access server high-availability deployment