New MP: System Center Management Packs for Data Protection Manager 2016 Reporting, Discovery and Monitoring


 

This download contains the management packs required to monitor and generate reports on Data Protection Manager(DPM) Servers using System Center Operations Manager.

 

Download HERE

Details

Note:There are multiple files available for this download.Once you click on the "Download" button, you will be prompted to select the files you need.

 

image

 

This download contains the management pack files (*.MP) required to monitor and generate reports on Data Protection Manager (DPM) Servers centrally using System Center Operations Manager (SCOM). The management guide document (*.docx) also provided with this download contains detailed instructions on how to set up, configure, deploy reporting centrally on the Operations Manager server and how to use the new enhanced extensible DPM Reporting Framework to generate custom agreeable reports. SC OpsMgr 2016 is required to be installed and running.

 

System Requirements

Supported Operating System

Windows Server 2012 R2, Windows Server 2016

 

Install Instructions

    Please download the Management Pack Guide (MP Guide_DPM2016Reporting.docx) available with this download and go through it carefully for detailed instructions and guidance.
    Also, select and download only the msi file with the name ending with your language-locale settings. For example, you will need to download SC Management Pack for DPM 2016 (ENG).msi if your language-locale setting is English (United States).
    Extract the msi file.
      You will find three (3) .MP files after extracting the msi. These MP files (Management Packs) need to be imported to your SCOM server carefully following the instructions given in the Management Pack Guide
      More from the Guide:

    Supported Configurations

     

    This set of management packs requires System Center Operations Manager 2016.

    The following table details the supported configurations for the Management Packs for Data Protection Manager 2016:

    Configuration

    Support

    DPM Reporting Management Pack

    5.0.1300.0

    DPM Discovery and Monitoring Management Pack

    5.0.1300.0

    DPM Library Management Pack

    5.0.1300.0

    Clustered servers

    Yes

    Agentless monitoring

    No

    Virtual environment

    Yes

 

Prerequisites

The following requirements must be met to run the discovery, library and reporting management packs:

· SC Data Protection Manager 2016 must be installed, up and running on all the DPM servers.

· If you want SLA data in DPM reports, Set SLA Requirements on the DPM Server using the PowerShell command-let :

Set-DPMProtectionGroupSLA –SLAInHours

If SLAs are not set on the DPM Servers, you will not get SLA Trends in the Reports.

· SCOM 2016 must be up and running.

· clip_image002

SCOM’s Data Warehouse should be up and running. To verify that, ensure that all the SQL Server services with the service name containing the SCOM DB Instance name are up and running. The screenshot depicting the list of running services below captures this scenario and your deployment environment must show a similar state before you proceed to install this MP.

Comments (16)

  1. JN says:

    Removing the old (2012 R2) management packs and importing the new ones worked, but it doesn’t look like the data warehouse is able to fully add in the reporting management pack (it doesn’t show up in the reports). There are 2 alternating alerts that keep popping up, one of which is the following:

    Data Warehouse failed to deploy database component. Failed to deploy Data Warehouse component. The operation will be retried.
    Exception ‘DeploymentException’: Failed to perform Data Warehouse component deployment operation: Install; Component: DataSet, Id: ’34f57e9b-2777-8c69-a5a6-fbc8d0f1824f’, Management Pack Version-dependent Id: ‘e3a96ce5-bfb2-07b8-ef66-4c711a6606c7’; Target: DataSet, Id: ‘3f4f9eb6-e811-4b90-a117-bf5fc4809b7b’. Batch ordinal: 8; Exception: Violation of UNIQUE KEY constraint ‘UN_StandardDatasetAggregationStorage_BaseTableName’. Cannot insert duplicate key in object ‘dbo.StandardDatasetAggregationStorage’. The duplicate key value is (tbl_DPM_BackupEvents).
    The statement has been terminated.

    One or more workflows were affected by this.

    Workflow name: Microsoft.SystemCenter.DataWarehouse.Deployment.Component

    Instance name: Data Warehouse Synchronization Service

    Instance ID: {5F80CF0E-D4C5-E494-E0EB-FAF66CE1AA40}

    The other is:

    Data Warehouse failed to deploy database component. Failed to deploy Data Warehouse component. The operation will be retried.
    Exception ‘DeploymentException’: Failed to perform Data Warehouse component deployment operation: Install; Component: DataSet, Id: ‘ee26b229-74db-718a-f5b5-fe951a02ea32’, Management Pack Version-dependent Id: ‘9e315942-a99b-8bb9-56d9-712f601901e7’; Target: DataSet, Id: ‘1853eddf-ec8d-4634-9e47-976b7d91207c’. Batch ordinal: 8; Exception: Failed to rename staging table as part of dataset maintenance. sp_rename returned ‘2627’
    Cannot grant, deny, or revoke permissions to sa, dbo, entity owner, information_schema, sys, or yourself.
    Cannot grant, deny, or revoke permissions to sa, dbo, entity owner, information_schema, sys, or yourself.

    One or more workflows were affected by this.

    Workflow name: Microsoft.SystemCenter.DataWarehouse.Deployment.Component

    Instance name: Data Warehouse Synchronization Service

    Instance ID: {5F80CF0E-D4C5-E494-E0EB-FAF66CE1AA40}

    The only references to anything similar I found stated that the user had to open a case with Microsoft to get it fixed. Is there anything I can do on my end to get this working?

    1. do you remember what information you had about the Microsoft case?

      1. MP says:

        I’m having these same issues, the only thing I could find was https://social.technet.microsoft.com/Forums/systemcenter/en-US/af4a28fb-3309-4a46-b47a-adc68ad67528/dpm-server-is-not-available?forum=operationsmanagermgmtpacks. It appears it’s not an isolated incident and opening a case should not be needed?

      2. André Moro says:

        The installation of Update Rollup 13 worked for me.

  2. The .docx states that SCOM 2016 is required but I could succesfully import this Management Pack into SCOM 2012.

    Is this a supported scenario?

    1. I have experienced the same thing; SCOM 2016 Management Packs appears work in SCOM 2012. Offically you have to go by what the Management Pack Guide states.

      I did not do any heavily monitoring with this management pack to verify everything works properly or what the difference is that requires SCOM 2016, but if you do I would monitor the management pack for a few days or week to make sure there is no issues.

  3. Tamas GAL says:

    I have an Discovery MP import error msg, what can I do?

    “This management pack cannot be imported.

    : Cannot load the management pack from the specified sealed assembly file: C:\Program Files (x86)\System Center Management Packs\Microsoft System Center Management Pack for DPM 2016 (ENG)\Microsoft.SystemCenter.DataProtectionManager.2016.Discovery.mp.
    This assembly is not fully signed. Cannot verify the strong name signature of the file: C:\Program Files (x86)\System Center Management Packs\Microsoft System Center Management Pack for DPM 2016 (ENG)\Microsoft.SystemCenter.DataProtectionManager.2016.Discovery.mp”

    1. Tamas GAL says:

      After 2 days is still awaiting moderation? I need some answer, pls.

      1. Try downloading it once more, hopefully what ever issue has been resolved. Another option is if you have your OpsMgr connected to the internet, you can import from the catalog.

        Please keep in mind, that blogging is on my own time and when I have time, just like every other Microsoft blogger. I typically work more than 12 hours a day, blogging is on my free time only.

      2. Tamas GAL, digging around and found a few threads talking about Windows Updates KB3194798, KB3192392, KB3185330 and KB3185331 breaks the SCOM 2016 and the SCOM2012 Consoles on all versions of Windows Server and clients.

        Here is a articles from a co-worker: https://blogs.technet.microsoft.com/germanageability/2016/10/17/october-2016-windows-patch-kb3192392-might-cause-scom-2012r2-console-to-crash/

    2. You’re not the only one having this issue. it appears others are too. I would try re-downloading it and re0importing it to verify.
      Hopefully the MP will get re-released very soon.

    3. Tamas GAL says:

      Dear Lynne,
      I appreciate very much your work, but it is extremely annoying that the SCOM 2016 around not really work at all (there is a critcal UI crash fault too). But for me next week to be presented on this subject several times. The re-download and install did not help.

      1. 16
        22

        Updated article 17.10.2016:
        This is just a short note that you should be careful installing the October 2016 cumulative Windows updates KB3194798/3192392/3185330/3185331 on Windows Server releases from 2008R2 up tp 2016 and Windows client releases from 7 up to 10 with the SCOM 2012/2012R2/2016 console installed on it.
        It might happen (in fact it will most certainly) that the console crashes regularly after the Patch installation.
        Update 19.10.2016 7:00 am (CET):
        The product group released a hotfix for this issue: https://support.microsoft.com/en-us/kb/3200006 . I have successfully tested it so far for Windows 2012R2 and SCOM 2012R2.
        This hotfix does not include a fix for Windows 10 1607 and Windows 2016. The product group is working on that as well with high priority, but there is no ETA yet. I will update this post as soon as there is a release date publicly available.

  4. Jimmy says:

    I get the following error:

    This management pack cannot be imported.

    : Cannot load the management pack from the specified sealed assembly file: E:\DPM\Microsoft.SystemCenter.DataProtectionManager.2016.Discovery.mp.
    This assembly is not fully signed. Cannot verify the strong name signature of the file: E:\DPM\Microsoft.SystemCenter.DataProtectionManager.2016.Discovery.mp

    1. It appears the cert is not able to be verified for the discovery mp. hearing this from a number of people as well. I would try re-downloading it again and re-import. hoping that this was corrected.

    2. Patrick Gemme says:

      I was getting the same management pack assembly file error about not being signed, but the new msi download link (top of this page) gave me packs that imported correctly.

Skip to main content