• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1179
  • Last Modified:

Exchange 2010 2 Server DAG - Do I really need CAS Array?

Ok, I have 2 Exchange 2010 severs clustered as a DAG.  Explain this to me like I'm a 6 year old: with 2010 clients and outlook anywhere web based clients why would I need a CAS Array? Newer Exchange clients attach to the RPC service and not directly to the CAS.  If one CAS goes down they automatically find the next RPC server.. correct?  If not why wouldn't the DAG internal IP address assigned to an MX record work?

Also, if you assign a CAS array I've read you don't need NLB...?
0
edutechceo
Asked:
edutechceo
  • 5
  • 4
3 Solutions
 
AkhaterCommented:
1st in exchange 2010 RPC connections are terminated directly on the CAS servers

>> If one CAS goes down they automatically find the next RPC server.. correct?
No not correct at all, in outlook configuration you have the name of your exchange server configured, if this is pointing to CAS server1 and this one goes down outlook will not look for any other

>>Also, if you assign a CAS array I've read you don't need NLB...?
wrong

Let me try to explain things in my own terms

a. Each Database has a property RpcClientAccessServer this entry points to the name of the CAS server responsible for this database. So when outlook is being configured autodiscovery service will fill outlook with the value in RpcClientAccessServer of  the database where the user's mailbox resides

b. technically speaking a CAS Array is nothing but a unified name you give to all CAS servers in a specific site and then change the RpcClientAccessServer property on all databases in this site to point to the name you have just created. the purpose, as you might imagine, is to make outlook connect to a unified name no matter how many cas servers you have in this site

c. Now that you have your casarray name you need to make this name resolvable by dns to the CAS servers in this site and here you have 2 options
    1. NLB: you setup an NLB between all these cas servers and you make the fqdn of your cas array point to the virtual ip of the NLB. however you should know that you cannot use Windows NLB if your CAS server is on a DAG member. if this your case you need to use hardware Load Balancer
    2. DNS Round robin: if you cannot use NLB you can use dns round-robin ( a lesser solution) which means  having 2 dns records in your dns for your cas array name each pointing to the IP of  one of your cas servers

Hope it makes more sense now
0
 
edutechceoAuthor Commented:
What about pointing the CAS array to the internal clustered IP address of the DAG?
0
 
AkhaterCommented:
you got the idea right but it won't work or at least not fully

it will give you high availability for your CAS but not load balancing
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
edutechceoAuthor Commented:
Ok - so it will try and connect to the DAG server that is up if one fails (CAS) if connecting to the DAG internal IP cluster network then?  If so this appears viable even without NLB - after all with 2 servers at the same site and 50 clients I'm not sure how NLB would be any better.

0
 
AkhaterCommented:
it means that when the 2 are up only one will be serving the 50 clients and not 25 clients on each as it would be the case in NLB
0
 
edutechceoAuthor Commented:
Makes sense - obviously spreading the load out with 50 clients is not really necessary - so if the clients will automatically find the other CAS in the DAG internal network (from the CAS Array assigned to the DAG internal net) then great.  Unless I'm missing a major downside to this.  At this point I guess round robin isn't necessary since it's one IP address...?
0
 
edutechceoAuthor Commented:
So is this correct - Round Robin isn't necessary since I'm pointing to the DAG internal cluster network IP or am I fooling myself here?  
0
 
AkhaterCommented:
in that case no need for round robin no just point the cas array name to the dag ip
0
 
edutechceoAuthor Commented:
That's what I'll do!  I'm going to implement this weekend...
0
 
Glen KnightCommented:
This question has been classified as abandoned and is being closed as part of the Cleanup Program. See my comment at the end of the question for more details.
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now