?
Solved

Exchange 2010 CAS without load balancer

Posted on 2014-10-24
7
Medium Priority
?
151 Views
Last Modified: 2014-11-29
I have Exchange 2010 SP3 with three servers in two separate sites. We originally designed with two servers and a single mailbox/CAS server in each site and DAG. All active databases are in the same site. To do maintenance or failover everyone would get the new CAS server when their mailbox failed over, and we would often times have to modify DNS for the CAS arrays because older Android clients didn't know how to fail over properly. We have now added a second mailbox server in the main site and I am thinking about how to add the CAS role quickly without requiring a hardware load balancer. My thought is to add the CAS role to the second server, and then just change DNS to point to one server or the other as required for doing maintenance or emergencies. I know that it isn't automated failover, and it isn't load balanced, and I am totally okay with that. I am just looking for a way to be less disruptive when I need to do maintenance on a server. Has anybody tried this, or know of why it would or wouldn't work? Eventually I would like to get Kemp. I know not to do round robin DNS.
0
Comment
Question by:kevinhsieh
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
7 Comments
 
LVL 44

Assisted Solution

by:Amit
Amit earned 1000 total points
ID: 40402980
You know answers to most of your question. In current environment, changing DNS record seems to be best option. I will say test the concept in test lab and then do it in production.
0
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40403140
Hey Kevin,

If you are looking for a temporary free solution I would look into ARR from Microsoft. It is a free plugin for IIS that allows you to do basic load balancing. You will need a separate box (or VM) to sit in front of Exchange.
http://www.msexchange.org/articles-tutorials/exchange-server-2013/mobility-client-access/iis-application-request-routing-part1.html
0
 
LVL 42

Author Comment

by:kevinhsieh
ID: 40403233
@Gareth, I have Exchange 2010 so there is client access using RPC in addition to https.
0
Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40403394
Doh! My apologies.
0
 
LVL 63

Assisted Solution

by:Simon Butler (Sembee)
Simon Butler (Sembee) earned 1000 total points
ID: 40403916
DNS entries with short TTL times are the answer here, both internally and externally.
Then you can make the required DNS changes when they are needed, and they will be picked up by the clients quickly.

Hopefully you have an RPC CAS Array for each AD site so clients can be moved around quickly.

Simon.
0
 
LVL 42

Accepted Solution

by:
kevinhsieh earned 0 total points
ID: 40463213
We have been able to do a poor person's CAS by configuring two CAS servers, and then changing DNS as needed to point users to one server or the other. Our public DNS service through DNSMadeEasy even handles the public DNS changes for us, which is a major win so that I only need to worry about the internal DNS.
0
 
LVL 42

Author Closing Comment

by:kevinhsieh
ID: 40471391
If properly configured CAS servers are in the same site, you can direct clients to one server or the other (or both using round robin DNS) via DNS without the need for a proper load balancer. I load balancer would be better, but DNS makes a nice substitute, especially if the primary issue is for maintenance and not automated high availability.
0

Featured Post

NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article will help to fix the below errors for MS Exchange Server 2013 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
This video discusses moving either the default database or any database to a new volume.
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
Suggested Courses

762 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