Microsoft Exchange on two sites for redundency and ease of access

Posted on 2012-08-14
Last Modified: 2012-09-28
We are small business with 55 employees. We have two offices the main offices. The main office has 40 employees and the branch office has 10-15 employees. We need to be able to automatically switch servers when there are issues in any of the sites. We have had a lot of issues with whether the past year where the main site has been down and we have no email. There has been times that the branch office has been down as well.  So, I like to know some options that would take care of this issues without the users being effected.
Question by:netcomp
    LVL 13

    Expert Comment

    What version of Exchange?  Solutions vary with the different features in the Exchange versions.
    LVL 3

    Assisted Solution

    if you have local internet at both sites then you may like to consider a web based hosted exchange solution this would be more cost effective for the size of your organisation or even go down the office365 route.

    LVL 1

    Author Comment

    The solution has to be local and not cloud.  We don't have Exchange now as we are running Kerio Mail server, but we want to replace with Exchange and it can be enterprise if that's the only way to accomplish this.  I used to work at a company that any time the local exchange server went down at any of the offices, the users would automatically be switched to the mail server in the main office . I guess Exchange was somehow being replicated. At the same time, their OWA was also redirected which was function of Exchange.
    LVL 13

    Expert Comment

    Ideally, you'd set up a DAG (Database Availability Group) that was replicated between offices.  DAG's are available in Exchange 2010.

    What is DAG:

    A how to:

    You'd basically have two independent Exchange servers that replicated the Exchange Mailbox stores.  You can break the stores up by the location (Site A Mailbox Store hosted on Exchange Server in Site A and Site B Mailbox Store in Site B).
    LVL 33

    Assisted Solution

    Each version of Exchange has its clustering concept where in there would be automatic failover process configured


    Exchange 2003
    Concept of Exchange 2003 Clustering

    Deployment Guide

    Exchange 2007

    Concept of Exchange 2007 Clustering

    Deployment Guide

    Exchange 2010

    Concept of Exchange 2010 Clustering
    [url="" Deployment Guide[/url]

    LVL 8

    Accepted Solution

    Exchange 2010 DAG configuration is the way to go, but I would wait for the 2013 which is soon to be released.

    Featured Post

    What Should I Do With This Threat Intelligence?

    Are you wondering if you actually need threat intelligence? The answer is yes. We explain the basics for creating useful threat intelligence.

    Join & Write a Comment

    Check out this infographic on what you need to make a good email signature that will work perfectly for your organization.
    Local Continuous Replication is a cost effective and quick way of backing up Exchange server data. The following article describes the steps required to configure Local Continuous Replication. Also, the article tells you how to restore from a backup…
    To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…
    The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

    732 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

    Need Help in Real-Time?

    Connect with top rated Experts

    17 Experts available now in Live!

    Get 1:1 Help Now