HOWTO: Exchange 2003 Redundancy

Posted on 2007-07-29
Last Modified: 2012-06-27
Windows Server 2003 Enterprise
Exchange Server 2003 Enterprise

I have a domain with two domain controllers, one of the controllers has exchange installed on it.  I am looking for redundancy for exchange and have seen clustering options and 3rd party software for replication, not really looking forward to the clustering and haven't seen any pricing on the sites for the replication software.

Would it be ok to install a second exchange server on the other domain controller?  What could be possible problems here?  I have never done this so I'm not even sure where to start.  Problem being if I did install exchange on another server, the server name would be different so if I tried a restore of exchange database it would fail.  What can I do here to give exchange some redundancy and minimal down time if I had to setup exchange on completely different hardware?
Question by:lee_connell
    LVL 15

    Expert Comment

    It's fairly pointless putting Exchange on the other server because all the resiliency you're going to get is with the Public Folders. You can's replicate mailboxes or run hot standby or anything.
    What you need to decide is what level of resilience you require.
    If you don't know or aren't experienced with clustering then you mustn't go near it. A cluser is easy to install and configure but you need some pretty decent skills to keep a server up and running.
    Less challenging is one of: DoubleTake, WANSync or alternatively a recovery package such as AppAssure or Microsoft DPM to enable (pseudo SAN quality) recovery at the block level.


    Author Comment


    I've seen WANSync, do you have rough guess of cost for these types of products?

    Also, currently one of my servers is old and I want to move exchange off to another server which already exists.  The name of the server is going to be different as well as the hardware.

    Can I install exchange onto this new server and then migrate the mailboxes over from the original server without any problems?

    If I can do that, how do I properly remove the original exchange server from the domain?
    LVL 15

    Accepted Solution

    None of the sync/replication products are very expensive; they all come in at a handful of thousand dollars per server. They're all cheaper than deploying a formal cluster.

    Introducing a new Exchange server and carrying out mailbox moves is extremely easy. There are guides at and to let you do that.
    Server Move:
    Remove first Exchange server:

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Free book by J.Peter Bruzzese, Microsoft MVP

    Are you using Office 365? Trying to set up email signatures but you’re struggling with transport rules and connectors? Let renowned Microsoft MVP J.Peter Bruzzese show you how in this exclusive e-book on Office 365 email signatures. Better yet, it’s free!

    Resolve Outlook connectivity issues after moving mailbox to new Exchange 2016 server
    Use these top 10 tips to master the art of email signature design. Create an email signature design that will easily wow recipients, promote your brand and highlight your professionalism.
    To show how to generate a certificate request 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 Servers >> Certificates…
    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

    779 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