Last week I attended an interesting session on Exchange 2010 monitoring and backup with System Center host by the System Center Influencer guys (https://connect.microsoft.com/SystemCenterCommunity?wa=wsignin1.0).
Two main topics has been covered:
- The new Exchange 2010 Management Pack for OpsMgr
- Using DPM to backup Exchange 2010
In this post I will focus on the first topic, but I want to add that you should take a serious look at DPM and when you do this, please try to have a new perspective. Do not try to map what you’re currently doing with your backup and recovery solution to DPM, rather you should learn DPM paradigm and see your data assets in this new perspective. It is a new backup paradigm and you’ll need to do things differently… the worst DPM implementations I saw were the ones where DPM has been used like a "traditional" backup software. Not the way to go.
The only pitfalls I must make you aware of is that you need to wait for the next version of DPM to protect Exchange 2010, and this is a pity given the tons of functionality in DPM and the fact that current DPM users must delay Exchange 2010 adoption ’til the release of DPM.
Returning to OpsMgr, the MP has been released soon after Exchange 2010 delivery, in this case we have no road block. We can adopt Exchange 2010 and being able to monitor it with our current OpsMgr infrastructure.
SO what’s new in this MP:
· Alert correlation
· Alert classification
· Mail flow statistics reporting
· Full protocol synthetic transaction coverage
· Service-oriented reporting
· Exchange aware availability modeling
The most interesting stuff in there is the new correlation engine, it’s a stand alone service that help reducing noise and who is in charge of generating alerts into OpsMgr via the SDK. A brand new approach in MPs and something I will return on in future posts.
This posting is provided "AS IS" with no warranties, and confers no rights.