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

HOWTO: Exchange 2003 Redundancy

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?
  • 2
1 Solution
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.

lee_connellAuthor Commented:

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?
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 www.swinc.com and msexchange.org to let you do that.
Server Move:
Remove first Exchange server:
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

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