Problem with DPM 2012 R2 console after install RU5

February 14th, 2015

The Data Protection Manager console is unresponsive after installing Update Rollup 5


After installing Update Rollup 5 for System Center 2012 R2 Data Protection Manager and performing inquiry on either the local DPM server itself or on another attached DPM server (for secondary protection), you notice that the console crashes, and upon starting it again it is unresponsive and hung at one of the following windows. You notice that cmdlets are also unresponsive.




More Information

Steps to reproduce this behaviour

Scenario 1

1. You have never protected the local DPM server’s System State with the DPM server itself and have protected System State/Bare Metal Recovery for other production servers.

2. You upgraded to DPM 2012 R2 UR5 and triggered an inquiry on the DPM server itself either from the UI (by expanding\refreshing the DPM server in the Create Protection Group Wizard) or by executing cmdlets.

Scenario 2

1. You have a primary DPM server protecting the System State of a production server.

2. You have attached the primary DPM server to a secondary DPM server for secondary protection (Disaster Recovery)

3. You upgrade the secondary DPM server to DPM 2012 R2 UR5.

4. You trigger an inquiry on the primary DPM server in the secondary DPM server UI (by expanding\refreshing the DPM server in the Create Protection Group Wizard) or by executing cmdlets.


Please use the following steps to correct an issue in the DPM database that causes this behaviour:

1. Stop the following DPM services (from the Services MMC SnapIn by running services.msc) in this order:

a. DPM AccessManager Service

b. DPM

c. DPM Writer


2. Open the SQL Server Management Studio (from either the Start Screen or by running ssms.exe)

3. Connect to the SQL Server Instance hosting the DPM database

4. Locate the correct DPM database in the instance (name starts with DPMDB)

5. Important! Take a full backup of the database by using the following steps to able to revert changes in case you incorrectly apply any further steps:

a. Right click the database and select Tasks->Back Up

b. Choose the Backup type as “Full” and backup destination to safe location on the Disk

c. Click ‘Ok’ and make sure the backup completes successfully

6. Now run the clean-up script by using the following steps:

a. Right click the database again and select “New Query”

b. Paste the following SQL script:

DELETE FROM dbo.tbl_IM_ProtectedObject

WHERE ProtectedObjectId IN


SELECT PO.ProtectedObjectId

FROM dbo.tbl_IM_ProtectedObject AS PO

JOIN dbo.tbl_AM_Server AS SRVR

ON PO.ServerId = SRVR.ServerId

WHERE (CONVERT(VARCHAR(4096),PO.ComponentName) = ‘System State’ OR CONVERT(VARCHAR(4096),PO.ComponentName) = ‘Bare Metal Recovery’)

AND PO.ProtectedInPlan = 0

AND PO.ProtectedObjectId NOT IN (SELECT ProtectedObjectId FROM dbo.tbl_IM_ProtectedObjectAlerts)

AND LOWER(CONVERT(XML,PO.LogicalPath).value(



)) != LOWER(SRVR.ServerName)


c. Execute the query by pressing F5

d. Make sure that the query is executed successfully. Depending on your setup, it will output a message showing the number of rows affected.

7. Now go back to Services SnapIn to start the services in this order:

a. DPM

b. DPM AccessManager Service

c. DPM Writer


8. Now open the DPM console UI. It should work normally as before.

Update Rollup 5 for System Center 2012 R2 Data Protection Manager is now available

February 14th, 2015

Update Rollup 5 for System Center 2012 R2 Data Protection Manager .This is a feature-rich release and an important milestone in our cloud integrated backup vision. In the coming weeks, we will publish detailed blogs and videos of the new features, keep watching this space for more! Azure is an integral and important part of this update rollup. Every feature of this update has an element of Azure plugged in to it. Customers will experience similar functionality and a more seamless experience irrespective of whether their data is protected locally or to the cloud. We have enabled more features for customers who are already using Azure for their long term backup & retention needs. If Azure is not an integral part of your DPM led backup strategy, this release still provides a compelling value prop.

Why Update Rollup 5

  • Azure is an integral and important part of this update rollup
  • Support for new workloads
  • Better data transfer and retention options to Azure
  • Enhanced monitoring and alerting
  • Useful Links

    1. Description of Update Rollup 5 for System Center 2012 R2 Data Protection Manager
    2. Download the Data Protection Manager update package now.
    3. DPM team Blog about UR 5

    New in Windows Azure (VM Security Extensions)

    June 26th, 2014


    During TechEd NA 2014 , Microsoft announced bunch of new features that are supported by windows Azure ,  some of these new features are (VM Security Extensions, ExpressRoute GA, Reserved IPs, Internal Load Balancing, Multi Site-to-Site VPNs, Storage Import/Export GA, New SMB File Service, API Management, Hybrid Connection Service, Redis Cache, Remote Apps).

    one of my favorite feature is  VM Security Extensions.

    VM Security Extensions:  These extensions offer a richer security protection to the VMs hosted in Azure using industry security products. Currently there are new three extensions for Microsoft Antimalware , Symantec Endpoint Protection and TrendMicro’s Deep Security Agent.

    To enable any one the above extensions, login to  Azure Management Portal and check the extension when you create new a new Virtual Machine:


    but wait you can enable these extensions from Power shell , the following cmdlets are available



    AlwaysOn Protection With System Center Data Protection Manager 2012 R2

    April 27th, 2014


    I have been waiting for months to write this blog about how to protect AlwaysOn with DPM , the reason for the delay that DPM 2012 R2 before RU2 wasn’t supporting AlwaysOn  with Cluster. 

    for Enterprises looking for true disaster Recovery and avoid single point of failure,  AlwaysOn can be setup using SQL Cluster Instance with a stand alone SQL server Instance.meaning the primary replica is hosted on a SQL Cluster instance and Secondary replica is hosted on SQL Instance Standalone. the reason for that is to avoid the single point of failure such as the SAN

    As I mentioned earlier , before DPM rollup Update 2 for System center , DPM didn’t support Protecting AlwaysOn with Cluster Setup.

    First step:  Install DPM Client to your WFC nodes , make sure to patch your DPM server with the latest RU2


    Second Step: Create a Protection Group to protect databases on Clustered AlwaysOn .


    Update Rollup System Center 2012 R2 is Now Available

    April 23rd, 2014


  • Data Protection Manager — KB2958100,
  • Operations Manager — KB2929891,
  • Orchestrator — KB2904689,
  • Service Manager — KB2904710,
  • Service Provider Foundation — KB2932939,
  • Virtual Machine Manager — KB2932926
  • Chocolatey for Open Source

    April 21st, 2014



    DPM Installation Error ID:820

    April 19th, 2014


    When you install DPM 2010, right after the prerequisites  verification you receive an error  “Verify that Windows Management Instrumentation (WMI) Service is running. if…


    in order to fix this issue, you need to reinstall WMI , this is how to do it

    From an elevated Command Prompt

    1. Disable and stop the WMI service.

    sc config winmgmt start= disabled

    net stop winmgmt

    2. Rename the Repository folder under C:\Windows\System32\wbem to Repository.old

    3. Run the following commands.

    Winmgmt /salvagerepository %windir%\System32\wbem

    4. Re-enable the WMI service and then reboot the server to see how it goes.

    sc config winmgmt start= auto

    Management Pack Development Training

    April 17th, 2014

    System Center 2012 R2 Operations Manager Management Pack




    Microsoft Azure Brazil South region is now in public preview.

    April 17th, 2014



    DPM 2012 R2 Support Windows 2003 server

    April 17th, 2014


    Don’t be surprise , DPM 2012 R2 doesn’t support Windows server 2003 ,   the rollup update is coming shortly and it will fix the issue.

    I know if Shreesh said that it will happen :)