Exchange 2010 Secondary Server / Redundancy

Posted on 2010-01-10
Medium Priority
Last Modified: 2012-05-08

I'm trying to implement Exchange 2010. I have a single server, which has a typical install, mailbox, client access and hub transport roles. It is also a DC. I have a single static IP and DNS is configured for this server on the network and ports 25 and 443 forwarded on the router, all works fine, but need a backup plan if this server goes offline for any reason.

So... if this server goes offline, what is the best way to implement a second server so that can take over the roles of the first server automatically, ideally so clients can still access e-mail until the server is back online, or as a minimum just so e-mails are being recieved until the main server is back online.

I would ideally like to do this with a minimum of two machines, one physical and one virtual...more virtual if really neccessary.

I've looked at DAGs, but seems to ideally implement this, you need the DC, CAS and Hub Transport and a minimum of 2 mailbox roles all on seperate machines.

I've also thought about setting a virtual machine with exactly the same settings etc as the main server, which is just switched on when the main server is offline, and port forwarding changed and carries on as normal, but would ideally want an automated solution, if this happens in the middle of the night for example.

I've also thought about installing another phone line and having another static IP, which is set as the mail2.domain.com MX record for example incase the first server can't be reached. Or how would I do this on the same network with the single IP?

What is the "correct" way to do this?

Any advice gratefully received...
Question by:johnsy32
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
1 Comment
LVL 33

Accepted Solution

Busbar earned 1100 total points
ID: 26277192
High availability consists of several compoenets at different level.
for HUB/CAS availability you need another hub/cas server that can take the work in case of the other server failure, in order this to work correctly you will need NLB.

for mailbox server you need to protect the server and the database contained in te mailbox server, another mailbox server with a DAG could be an option, another option is to have another mailbox server and backup the database, in case of failure you can use the DB portability feature to restore the backup sets.

you can use 2 server scenario where you can host on each server hub/cas/mailbox and configure a DAG, and don't provide HUB/CAS high availabilty using NLB, and use manual configuration to do HUB/CAS reconfiguration in case of the server failure.

Featured Post

Industry Leaders: 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

This article lists the top 5 free OST to PST Converter Tools. These tools save a lot of time for users when they want to convert OST to PST after their exchange server is no longer available or some other critical issue with exchange server or impor…
How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…
This video discusses moving either the default database or any database to a new volume.
Suggested Courses

777 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