Automatically recovering after storage failures

Exchange 2013 further improves the bug check behavior introduced in Exchange 2010 by including features that allow for self-recovery when certain failures happen. It now checks for excessive memory use by the Replication service and long I/O times, among other checks.

As an example, because the Crimson channel is a crucial component for normal operations, the Replication service checks every 30 seconds if it can be accessed. If the Crimson channel is not available, maybe due to a failure with the event channel for example, the Replication service tries to recover the server by rebooting it, which triggers a failover.

Note

Windows Server 2012 has two categories of event logs: the traditional Windows logs that include the usual Application, Security, and System event logs, and Applications and Services. Applications and Services logs are a new category of event logs used to store events from a single component or application, such as Exchange in...