Responding to Managed Availability
I’ve written a few blog posts now that get into the deep technical details of Managed Availability. I hope you’ve liked them, and I’m not about to stop! However, I’ve gotten a lot of feedback that we also need some simpler overview articles. Fortunately, we’ve just completed documentation on TechNet with an overview of Managed Availability. This was written to address how the feature may be managed day-to-day.
Even that documentation doesn’t address how you respond when Managed Availability cannot resolve a problem on its own. This is the very most common interaction with Managed Availability, but we haven’t described how specifically to do so.
When Managed Availability is unable to recover the health of a server, it logs an event. Exchange Server has a long history of logging warning, error, and critical events into various channels when things go wrong. However, there are two things about Managed Availability events that make them more generally useful than our other error events:
- They all go to the same place on a server without any clutter
- They will only be logged when the standard recovery actions fail to restore health of the component
When one of these events is logged on any server in our datacenters, a member of the product group team responsible for that health set gets an immediate phone call.
Please review the complete blog at https://blogs.technet.com/b/exchange/archive/2013/12/16/responding-to-managed-availability.aspx
Read my favorites blogs:
Assigning File Share permissions using Power Shell
Designing a backup less Exchange 2010 Architecture
Microsoft Exchange 2010 CAS Array – Steps and Recommendations
Appear Offline in Microsoft Office Communicator Server 2007
Microsoft Exchange 2010 Test cases