Exchange Server disaster recovery plan considerations

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Microsoft Exchange Server Backup and Disaster Recovery Fixing DPM 2007 inconsistent replica errors in Exchange Server New high availability features in Exchange Server 2010 Restore contacts from an Exchange public folder Exchange Server 2007 SP2 reinstates built-in backup capabilities Working with continuous replication in Exchange Server 2007 How a bare-metal restore affects Microsoft Outlook 2007 performance Testing a passive database for corruption in Exchange Server 2007 Implement CCR to improve Exchange Server 2007 mailbox reliability Use the RecoverServer switch to rebuild a failed Exchange 2007 server Recovering deleted items after an Exchange 2003 migration Microsoft Exchange Server Backup and Disaster Recovery Research David Sengupta: Server Administration Changing email address formats in Exchange Server 2003 Should you remove .STM files from Exchange Server 2003? Exchange users receiving email addressed to legacy users Pushing a public calendar out from a private Exchange account Import and export .PST files in Exchange Server 2007 Editing Exchange Server public folder permissions Search and index Microsoft Outlook 2007 public folders Troubleshooting Microsoft Exchange Server Event ID error 6009 Can't delete old Microsoft Outlook public folders Can't create mailboxes after virtualizing Microsoft Exchange Server

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

The most important thing is that you test your Exchange Server disaster recovery (DR) plan a few times to confirm that everything works as intended. What you propose sounds fine in principle, but you need to test to ensure you have all the details worked out.

One thing you may want to consider: some third-party utilities on the market circumvent the requirement for an Exchange recovery server. In essence this allows you to stand up any 'cold' or 'warm' site and then import the mailboxes directly from backup media to the production server, without a need for recovery servers and associated recovery steps. I'm assuming you have a Service Level Agreement (SLA) of some sort in place (or at least implied expectations). These will dictate how much you streamline the overall DR process outlined in your plan.

Of course, much more is involved in this process. I've seen consultants spend weeks working with customers to develop an Exchange Server DR plan -- from making sure software media and licenses are in place to documenting your backup rotation and offsite storage -- through documentation of all elements of people, process and technology required for successful execution of the DR plan.

Do you have comments on this Ask the Expert Q&A? Let us know.

Related information from SearchExchange.com: