Chapter 9. Planning a Highly Available Exchange Server 2007 Implementation
Implementing load balancing
Implementing single-copy clustering (SCC)
Implementing DNS round-robin
Implementing multiple Mail Exchanger (MX) records
Planning data-redundancy implementation
Implementing local continuous replication (LCR)
Implementing cluster continuous replication (CCR)
Using Dial Tone recovery
Implementing database portability
Planning the Service's High-Availability Implementation
Messaging-service availably can be affected in a large number of ways. Being aware of these factors and how to mitigate them is important when designing a plan for high availability. Adopting good patching and maintenance procedures will go a long way in keeping your messaging platform stable. (You can find more information on patching in Chapter 17 of this book.) No matter how many procedures you adopt, a flawed design can still cause undue frustration. It is important to be aware of any single point of failures in your environment. Care should be taken to choose hardware that best meets the availability requirements. Having redundant power supplies and hot-swappable disk drives in a RAID (redundant array of independent disks) set are important considerations. Also, improperly sized hardware can cause service outages when load exceeds the capacity of the server. Exceeding load can happen when the processors or memory aren't ...
Get MCITP: Microsoft® Exchange Server 2007 Messaging Design and Deployment: Study Guide now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.