Problem with DPM 2012 R2 console after install RU5

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

Symptoms

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.

clip_image002

clip_image004

clip_image006

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.

Resolution

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

d. DPMRA

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(

‘(/child::ArrayOfInquiryPathEntryType/child::InquiryPathEntryType[attribute::Type="Server"]/attribute::Value)[1]‘,

‘VARCHAR(4096)’

)) != 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

d. DPMRA

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

Comments are closed.