Article ID: 2809773 - View products that this article applies to.
After installing Update Rollup 3 for System Center 2012 Data Protection Manager
(http://www.microsoft.com/en-us/download/details.aspx?id=35372)you notice that the DPM database grows and eventually the DPM console will crash.
This issue is caused by a regression introduced in Update Rollup 3 for System Center 2012 Data Protection Manager.
This issue has been corrected in System Center 2012 Data Protection Manager 2012 Service Pack 1
(http://blogs.technet.com/b/dpm/archive/2013/01/15/system-center-2012-sp1-data-protection-manager-is-generally-available.aspx)(SP1) or you can use the following workaround:
1. Backup the DPM Database.
2. Execute the following SQL stored procedure:
/****** Object: StoredProcedure [dbo].[prc_PRM_SharePointRecoverableObject_Update] Script Date: 11/03/2012 01:36:08 ******/
SET ANSI_NULLS ON
SET QUOTED_IDENTIFIER ON
ALTER PROCEDURE [dbo].[prc_PRM_SharePointRecoverableObject_Update]
DECLARE @error INT,
SET @error = 0
SET NOCOUNT ON
-- UPDATE tbl_RM_SharePointRecoverableObject SET Caption = @Caption
UPDATE tbl_RM_SharePointRecoverableObject SET Caption = @Caption,
ComponentType = @ComponentType
WHERE RecoverableObjectId = @RecoverableObjectId
SELECT @error = dbo.udf_DPS_CheckRowCount(1)
SET NOCOUNT OFF
3. Finally, execute this following stored procedure.
SET ROCatalogCheckPoint = NULL
WHERE DatasourceId IN
(SELECT DISTINCT ReferentialDatasourceId FROM tbl_IM_ProtectedObject
WHERE ReferentialDatasourceId <> NULL)
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Contact us for more help
Connect with Answer Desk for expert help.