Providing redundancy to Exchange server 2003 Standard Edition

Posted on 2009-05-11
Last Modified: 2012-05-06
Hi All,
I need to come up with a solution for proviidng redundancy for a small organisation (about  20 users) who runs Exchange 2003 (Standarad).  This server is a DC. The organisation can tolerate a outage of some 4-5 hours (say 1/2 a working day).

Clustering is out of the scope. I have read about Double-Take, however, given the service outage window the organisation can tolerate, I thought maintaining a server as a hot standby to be a cost effective approach -  basically to build another Exchange 2003 Server box  and to copy across exchange mailboxes/database twice a day or so. What would be the best way (software)  to implement such a solution - obvioulsy hardware will be dissimilar.
Question by:lakshmanl
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

Expert Comment

ID: 24361312
another solution might be to use mail bagging, you can have your users check webmail in case of an emergency.  Clustering is the way to go even though its out of the question, a hot standby might be too much work.
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 24361785
Humm a good option would be if you can think of upgarding to Exchange 2007 Sp1. As you now can use LCR (Single machine) and SCR (Source and Target) features and no need to copy paste data twice a day even with Standard version.
You can also look for some articles at and for LCR and SCR, as they both are high availability features also you in case your production database goes down you dont have to restore and can get everythingh back much faster.
Hope that you would be glad to know and get a chance to work with it.
LVL 65

Accepted Solution

Mestha earned 400 total points
ID: 24363409
Exchange 2003 doesn't really have any kind of hot features, because the database is tightly tied to the name of the machine it comes off. You also would have to dismount the database completely to copy the files across, and the Exchange database is not designed to be repeatedly mounted and dismounted. That can lead to corruption.

DoubleTake is probably going to be your best option here if you want something that is more frequent than backups. Exchange 2007 would be ideal but you are looking at two new Exchange 2007 licenses, CALs and hardware. Another option would be SBS 2008 and an additional Exchange 2007 license. At 20 users it is the most cost effective way of getting the base license.

Otherwise, given the downtime window, simply having another machine built, but not with Exchange installed or joined to the domain might be enough. In the event of a problem with the original, the replacement is used in a full DR restore and the backups used. However that depends on what you are planning for. Backups are a point in time snapshot, but for most companies the most valuable email is that which has been received in the last 24 hours. Those are held in the transaction logs.

Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.


Author Comment

ID: 24370322
Hello All,
The organisation have a raft of public folders and hence I was shying away from Exchange 2007. Also, I read somewhere that you cannot do an in-situ upgrade (just upgrade Exchange 2003 to 2007 on the same box).

Now I am more thinking towards Double-Take. Am I right in thinking that the fail-over box I have to configure would have to have the same machine name, and IP#? If this is the case, how do I go about setting up - It has to be on the network for Double-Take to do it's job, isn't it? I don't have any experience with Double-Take.

Thanks and Regards
LVL 65

Expert Comment

ID: 24370366
For Exchange 2007 there are no in place upgrade options. It is a different architecture. The only options are swing.

Doubletake is a complete mirror, and it has to be on the network live. It isn't really a product you would buy off the shelf and install, I would suggest talking to their people about the nuts and bolts of what is involved. DoubleTake deals with the machine name, IP address work etc.

LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 24372344
If you are going to use Double-Take, so the best i would suggest is to have a word with those guys and get the information about the configuration and how about the usage (i mean setup and failover and other stuff)
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 24442136
Any updates on the issue ?

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

Read this checklist to learn more about the 15 things you should never include in an email signature.
There are times when we need to generate a report on the inbox rules, where users have set up forwarding externally in their mailbox. In this article, I will be sharing a script I wrote to generate the report in CSV format.
In this video we show how to create a Shared Mailbox 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 Recipients >> Sha…
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit If you want to manage em…
Suggested Courses
Course of the Month10 days, 19 hours left to enroll

628 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