June 2007
Intermediate to advanced
720 pages
20h 39m
English
In all situations that require high availability, it’s best to establish more than one point of failure. Case in point—a parachute. If one chute fails to open, there is a secondary chute. The same thinking holds true in airplanes, whether it is redundant engines, fuel lines, even pilots that are required to eat different types of meals—no single point of failure.
Within your Exchange organization, the key to high availability extends to more than just your Exchange servers. Your Exchange servers may function perfectly, but you might lose availability to them if a dependent ...