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

New Exchange Server Installation

I am looking at implementing exchange server and migrating all the mailboxes from the cloud to the in house environment. I would like to implement fault tolerance. I will be installing Fault tolerance HDD PSUs. I am looking at a failover such as a clustered hyper-v box , or just 2 exchange environments. I would appreciate your thoughts/experience on this, is there a best practice guide?
  • 2
1 Solution
AmitIT ArchitectCommented:
For best fault tolerance, you need below three things
Server, Disk and site Resilency

With Exchange 2007, you can implement CCR.
With Exchange 2010, you can implement DAG.

Best practice again depends on budget. But as far I can recommend

1) Mailbox and Unified roles, keep them on Physical server
2) Hub/CAS can be on VM
3) For HUB fault tolerance, you need to implement Hub server in each site
4) For CAS, you can use NLB or Hardware load balancer like F5, Big IP or Barracuda. Hardware will be better.
5) You can also use CAS array, but again it is not 100% fault tolerant, in case of any failure you just need to repoint the DNS to second CAS server.

Hope this helps

AmitIT ArchitectCommented:
Forget to add the Backup part.

1) Mailbox : Take backup from passive node. You can use Symantec or Windows Backup
2) HUB/CAS: Do need any back, in case of failure, you can do the disaster recovery with recoverswitch
3) If you made any customization for OWA, then you need to take that backup.

Hope, i have given lot of information
DanJEvansAuthor Commented:
Thank You for you help.
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

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

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