Best Practice #5: Configuring Exchange for disaster recovery

Article

Best Practice #5: Configuring Exchange for disaster recovery

Richard Luckett
Exchange Server 2000/2003 has built-in capabilities that can be taken advantage of to reduce single points of failure and facilitate the disaster recovery process. However, the Enterprise Edition of Exchange Server 2000/2003 includes extra features not available in Standard Edition.

Enabling each of the following Exchange features could be considered a best practice:

    Requires Free Membership to View

    Login

    When you register, you’ll also receive targeted alerts from my team of editorial writers and independent industry experts with the latest news, tips, and advice to help you do your job more efficiently and effectively. Our goal is to keep you informed on the hottest topics and biggest challenges faced by Exchange professionals today working with Exchange, Outlook and other related technologies.

    Margie Semilof, Editorial Director

    By submitting your registration information to SearchExchange.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchExchange.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.


Premium Access

Register now for unlimited access to our premium content across our network of over 70 information Technology web sites.
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

  • to match your organizations data retention policy. By default, it is set to 30 days in Exchange Server 2003.

  • Put your transaction log files on a dedicated mirrored (RAID 1) volume.

  • Put the information stores for each storage group on a dedicated RAID 5 or RAID 0+1 volume. (Enterprise Edition only).

  • Divide your users' mailboxes up and spread them across multiple storage groups and mailbox stores (Enterprise Edition only).

  • Configure Status and Notifications to monitor server resources like memory, disk, and processor so that you can be notified when resource failure is looming.


Best Practices Checklist: Exchange Server disaster recovery planning

 Home: Introduction
 Best Practice #1: Understanding Exchange databases
 Best Practice #2: Building your plan around the technology at hand
 Best Practice #3: Keeping e-mail in perspective
 Best Practice #4: Configuring server hardware for disaster recovery
 Best Practice #5: Configuring Exchange for disaster recovery
 Best Practice #6: Simulating a disaster
 Best Practice #7: Learning from others' mistakes and successes
 Best Practice #8: Considering offsite storage and remote recovery
 Best Practice #9: Familiarizing yourself with the right resources

ABOUT THE AUTHOR:   
Richard Luckett, Vice President and Senior Consultant, Ajettix Security
Richard Luckett is a Microsoft Certified Systems Engineer on the Windows NT 4.0, 2000 and 2003 platforms and has been certified on Exchange since version 4.0. He is the co-author of Administering Exchange 2000 Server, published by McGraw Hill, and has written four Exchange courses, Introduction to Exchange 2000, and Hands-on Exchange 2003, Ultimate Exchange Server 2003 and Exchange Server 2003 Administrator Boot Camp for Global Knowledge Inc. Richard is currently Vice President and Senior Consultant for Ajettix Security, where he is the head of the Microsoft security practice.
Back to top