Exchange 2010 CAS Array two active sites

Posted on 2013-08-28
Medium Priority
Last Modified: 2013-08-29
Setup: Exchange 2010 SP3, windows 2008 R2 SP1
Data Centre
mbx01 - mailbox server
mbx02 - mailbox server
CAS01 - CAS/HT server
CAS02 - CAS/HT server

Head office
mbx03 - mailbox server
CAS03 - CAS/HT server

All active databases will be located at the Data Centre and a passive copy at the head office apart from head office users who's active database will be local and passive at the Data Centre

An F5 hardware loadbalancer is located at the Data Center and configured with CAS01 and CAS02 as the primary connections and if they are not available CAS03 as the tertiary.

Is this an acceptable configuration or shall I have all databases located at the Data Centre and head office as a DR site only with no active databases. Would make it easier in a DR situation.

How do I ensure that head office users connect to the local CAS Array instead of going across the WAN or does Outlook always look at the local site CAS first?  

In the event we lose one site how will the failover occur?
Question by:ITISEMEA
  • 5
  • 4
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39445371
Trying to do Active/Active across two locations rarely works well. The most likely problem is loss of the connection between the sites and in that scenario one location would be down, because quorum would be lost.

Personally I would redesign the platform to have all three roles on all the servers.
Have two DAGs, using three servers for each DAG. Two active in each site, with a single passive in the other. Each location would have its own CAS Array.

Remember CAS/Hub roles do not belong to any mailbox server, so the server can be used by users of DAG 1 while holding a database from DAG 2.

You haven't said how many users are involved, but I haven't done a design for less than 10,000 users in the last 18 months with seperate Mailbox and CAS/Hub.


Author Comment

ID: 39445418
Hi Sembee2

thanks for the quick reply. we have 1700 mailboxes.
makes sense regarding the site fail over and quorum.

90% of users will be accessing the mailboxes via the Data Centre therefore the head office will be the DR site.
considering i have an F5 in the scenario how would you suggest i configure the CAS array.

Data Centre - casrarray1.domain.local
head office casarray2.domain.local
DNS records for each name in AD
F5 pointing primarily to casarray1.domain.local and if they are not available point to casarray2.domain.local. in a DR event i would then follow the normal Exchange failover procedures?
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39445507
The RPC CAS Array is AD site specific.
Therefore as you have two sites you will need two CAS Arrays. In the event of a failover you would just move the DNS entry across to the other location.
Therefore the load balancer would just point everything to the server in the second location. The address the users are using to access Exchange with Outlook would not change.

Even with 1700 users I would still do the design I have outlined. I have just implemented (went live yesterday) 2500 users on the same design and it has worked exactly as planned.
You can even use the passive server in each location as the FSW for the active DAG, therefore keeping everything within Exchange.

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.


Author Comment

ID: 39445835
im still not certain about this F5 HLB configuration
i have a virtual IP ( from the F5 which points to CAS01 and CAS01 primarily and CAS03 if 01 and 02 are down.
A DNS record has been created called CASArray1.domain.local which point to
therefore if i also name the head office CASArray1.domain.local will the F5 not load balance this? Can you actually have the same name for a CASArray in different sites, will Exchange allow you do this.
LVL 63

Accepted Solution

Simon Butler (Sembee) earned 1700 total points
ID: 39445973
The CAS Array is just a DNS entry and a configuration on the database.
If you are pointing clients at the load balancer and the load balancer is pointing the clients at a server in another site, then that is fine. It will work correctly.

The CAS Array is AD site specific - when you create the entry you have to tell it what site it is in.


Author Comment

ID: 39448105
Hi Simon

I just wanted to give you an update. i tried creating a new CASArray in the head office using the same name as the Data Centre and received the following error

Active Directory operation failed on GBLON01ADC03.domain.local. The object 'CN=casarray1.domain.local,CN=Arr
ays,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=domain,CN=Microsoft Exchange,CN=S
ervices,CN=Configuration,DC=domain,DC=local' already exists.
    + CategoryInfo          : NotSpecified: (0:Int32) [New-ClientAccessArray], ADObjectAlreadyExistsException
    + FullyQualifiedErrorId : D947E4B1,Microsoft.Exchange.Management.SystemConfigurationTasks.NewClientAccessArray
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39448169
That is what I would expect. You cannot have two arrays with the same name. They must be unique. However you can, in the event of a failover, point the two arrays at the same CAS role holder.


Author Comment

ID: 39448177
sorry i must have miss understood your previous post. Does the name need to be unique throughout the exchange environment, forest or just domain. We have several exchange servers in the enviroment which are split accross subdomains
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39448187
The name and host name of the CAS array needs to be unique across the entire forest.
Where the Exchange servers physically are doesn't matter, as long as you have your AD Sites and Services setup correctly. If you have multiple subnets then you need to ensure that all of those are listed in AD sites and services and assigned to the correct site.

When I do multiple site implementations, we usually come up with a naming convention for the CAS array DNS entry.



It makes it very easy to manage and know what host is for which location.


Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

If there is anything erroneous with Exchange Database, it causes a significant effect on email communication till the user remounts the database. Further, database crash directly affects Outlook users due to which they are unable to access their ema…
In an Exchange Crossforest migration, the distribution groups can be a very complex operation that would cause loss of time, lots of issues and continued headaches if not solved in a timely manner. I had to do a similar project so I created a sc…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…

624 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question