DR Site for Exchange Server 2007 SP1
we already have installed Exchanage Server 2007. For this implementation, we have 5 servers. 3 of which are used for Mailbox Server our of which third mailbox server acts as HUB Transport Server as well. one server is used for Edge Server role. and Finally last server is used for CAS server Role. we have only one Domain setup. We are planning DR site for our Exchange Server. We have already procured same number of servers hardware (5) for our DR location. we are planning to have DR site on same Domain and we will be placing ADC at DR site.Kindly help in suggesting the best practices to setup DR site in the above mentioned situation.
October 4th, 2009 3:03pm
The Mail box servers in production site are clustered or stand alone servers?? If Stand alone, i will recommned to put them first on cluster (CCR or SCC) and then plan for DR. On DR you can for SCR which will give you fair amount of DR functionality with log shipping etc. or else if you guys are going on server 2008 as server OS, go for Geo Clusters with one node each for production and DR.Have a look into this http://technet.microsoft.com/en-us/library/aa998848.aspx
Raj
Free Windows Admin Tool Kit Click here and download it now
October 4th, 2009 4:17pm
If you're planning on a DR Site, take a look at Standby Continuous Replication (SCR). SCR allowst you set up either a standalone mailbox server (non-Clustered) in which you can recover using database portability or you can opt to use a standby cluster instead which can be either shared storage or separate storage. You can set up a Windows Cluster with Active/Passive but you can only install a passive Exchange node which prevents any CMS from being created and allows you to replicate to this node. Then when you need to recover to your DR site, you can recover your CMS. You can read more about SCR here: http://technet.microsoft.com/en-us/library/bb676502.aspx In regards to Geoclusters, one thing to keep in mind is that Geoclusters assume you have LAN type bandwidth/latency. There's a good article by HP which statistically talks about how latency is very important for log shipping to make sure your databases automatically amount. You can read that article here: http://h20195.www2.hp.com/v2/GetPDF.aspx/4AA1-4230ENW.pdf Some more information in regards to Geoclusters are here: http://www.msexchange.org/articles_tutorials/exchange-server-2007/migration-deployment/deploying-exchange-2007-multi-site-ccr-clusters-part4.html MVP | MCSE:M | MCITP: Enterprise Messaging Administrator | MCTS: OCS + Voice Specialization | http://www.shudnow.net
October 4th, 2009 6:44pm
You did not mentioned anything about your user number or requirements for the Exchange. So without these details one suitable solution is to create one CCR cluster using two of your MBX servers and then move all users to that server. Then change your HUB+MBX server to HUB+CAS. And also change your CAS to HUB+CAS. The problem on here is that all users are in the same server, but if that is not problem go and get it. I believe you are quite safe after this and no servers needed yet! :) To the DR site, buy three servers, 1. for SCR MBX, 2. for CAS + HUB and 3. edge. Assuming that you are going to get your the primary site up as soon as disaster hits. -- Petri
Free Windows Admin Tool Kit Click here and download it now
October 4th, 2009 9:43pm
If staying with Exchange 2007 is a requirement, SCR is the best bet. You didn't mention database size or user count, so I am not sure where you are on that, but you may want to consider waiting and using Exchange 2010's DAG technology to address both your DR issue and possibly repurpose all three MBX servers and the CAS server to hold all three roles on each and load balance as well as make your data more fault tolerant.
October 5th, 2009 6:09pm