Comments on: Suggestions to improve Exchange Server disaster recovery http://itknowledgeexchange.techtarget.com/itanswers/suggestions-to-improve-exchange-server-disaster-recovery/ Sat, 25 May 2013 00:24:16 +0000 hourly 1 By: dbtk http://itknowledgeexchange.techtarget.com/itanswers/suggestions-to-improve-exchange-server-disaster-recovery/#comment-59879 dbtk Thu, 12 Feb 2009 15:21:41 +0000 #comment-59879 In the name of full disclosure I work for Double-Take Software. Clustering is certainly a good solution for high availability and with the improvements with failover clustering it is even better able to help provide disaster recovery by removing some of the previous MSCS requirements like same subnet and 500MS UDP round trip. This can help you distribute the nodes between greater distances but you still have the shared storage requirement. Depending on your disaster recovery infrastructure, do you have a WAN, hotsite or sister office to use as a DR location, you could use host based asynchronous replication or even a hardware based sychronous replication solution that would replicate all changes from one location to another. Typically, in the event of a failure you simply redirect active/directory (automatically or manulaly) to point at that DR exchange server name which once the database is mounted will redirect users to begin using and can be available as little 5-15 minutes depending on how long it takes to mount the exhcnage stores. I know that MS has LCR and CCR functions to in Exchange 2007 that can help provide some features as well.

Those are a few options for Exchange DR.

Hope this helps,

]]>