Make sure you document all Exchange dependencies and have a documented strategy of how those services can be recovered....
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
The following are just some examples of the dependencies you should be prepared for:
- Storage Area Network (SAN)
- Windows Server 2003 (OS)
- IIS metabase
- Certification authorities (CA)
- Active Directory domain controllers
Best Practices Checklist: Exchange Server disaster recovery planning
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.