Disaster recovery protection for Exchange Server

20.01.2006
Microsoft Exchange server downtime costs companies millions of dollars a year. Technically savvy IT organizations are therefore working to eliminate or lessen the impact of both planned and unplanned downtime through the implementation of high-availability systems and disaster-recovery systems. However, building a geographically dispersed Exchange cluster is not a simple task; it requires proper planning, testing, deployment and validation. By understanding the issues raised in this discussion and considering these recommendations during the planning stage, you will have taken the first and most critical step toward deploying the system that best meets your business objectives.

The process begins with the initial decision to implement an Exchange disaster-recovery system and continues as long as that system is in production.

In the planning phase, you must answer these critical questions:

What is the recovery time objective for the system?

Based on the rate of change and expected growth, what bandwidth is required between the primary site and the disaster-recovery site?

What pieces of the system besides the Exchange server and processes themselves must be monitored and recovered? Is there a minimum set of functionality that's acceptable for some time following recovery? If so, what is that subset?