Tuning the DPM MP to avoid excessive CPU Usage


The brand new DPM MP is starting to become something usable. It completely lacks any serious performance collection for trending and statistics, but at least we have some decent monitors. From a backup system MP I need to have evidence of any substantial change in backup volumes and speed, just to cite an example. (Maybe I should work on it)

But what’s going to hurt you if you implement such an MP is an high CPU usage on your DPM servers caused by the logical disk monitoring of the OS MP. If you implemented DPM you know that every protected resource has it’s own disk, these disks are implemented as mounting points at the OS level. It’s not uncommon to have hundreds of such disks on a DPM Server. All these disks are discovered as logical disks and monitored the way logical disks deserve:

  • availability check every 5′
  • space availability check every 1 hour
  • avg disk seconds per transfer check every 1′

All these checks are implemented via WMI, so we have these wmi queries for hundreds of disks, guess what? Your cpu is constantly overloaded. Not taking into account the performance collection rules.

The solution is pretty easy, and immo should have been implemented in the DPM MP or at least documented in the MP guide. Since these disks are managed by DPM there’s no need to double check them, if any problem arises then the DPM MP will take charge of letting us know. Given this fact we can simply disable the “Mount Point Discovery Rule” (from the OS MP) for the group “DPM Server Group” (exposed by the DPM MP). And if you want to cleanup your console, don’t forget to run Remove-DisabledMonitoringObject from CommandShell.

Advertisements
  1. #1 by Mark Verbaas on February 2, 2009 - 10:07 am

    Thank you for this very usefull post. I’ve one questoin/comment, do I need to override all (in my case 6) discoveries? I’ve got discoveries for Windows Computer types (2003 and 2008); Windows Logical Hardware Component (2003 and 2008) and Windows Logical Disks (2003 and 2008).
    We’ve DPM servers on both OS’s.

    For now I will disable all.

    Best regards,
    Mark

    • #2 by Daniele Grandini on February 3, 2009 - 9:42 am

      Hi Mark,
      you just need to disable the Mount Point Discovery Rule for the DPM Server Group for WIn 2003 and 2008. To do that go to the authoring pane, scope the view for “WIndows Server 2003 Logical Disk” and “Windows Server 2008 Logical Disk” and you’ll find the two discoveries you need to disable.
      Regards
      Daniele

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: