DPMDB Database and Log File DPM 2012 get very big with lot's of Free Space in just one day

Hi,

Since around a week my DPMDB and log file gets so big i run out of space on my local hdd. I use a local sql instance 2008 r2 sp1. I run DPM 2012.

This morning the DB was 25GB with 76% Free Space. The Log was 45GB with 99% Free Space.

Only thing I can do is shrink both. But I can only do this after deleteing other stuff to make some room. So it's not a good situation.

Edit - It seems it has something to do with the SharePoint Catalog Task - Edit

I browsed a hyper-v server to recover a file some days ago. Can this be the cause?

I update to Rollup 3 a bit more then a week ago. Can this be the cause?

Anyone know of this?

Anyone has an idea how i can troubleshoot this?

All help appreciated.

DJITS.


  • Edited by DJITS Sunday, October 28, 2012 9:33 AM Adition
October 27th, 2012 9:43am

Hi Stephane,

I didn't run the SharePoint Protection Group last night and the databse stayed perfectly the same so it's definitely something related to the SharePoint Protection. I'll move the DPMDB to new storage by deinstall and reinstall and then i'll run the SharePoint Protection Group with the SQL Server Provider.

Keep you updated.

Edit - I Reinstalled DPM 2012 Rollup 3 on new storage, restored backup, run sync and consistency check and all was well till 11:00  evening yesterday. Then the Sharepoint Catalog job started again. This morning the DPMDB was 45GB, the Log was 45GB but the temb db (still on the c drive) was 96GB. Again no more disk space.

Here is the result of the query again (didn't shrink the db and log this time).

Any new ideas other then removing Rollup 3 and see if this helps?

DJITS


  • Edited by DJITS Tuesday, October 30, 2012 7:15 AM New Facts
Free Windows Admin Tool Kit Click here and download it now
October 29th, 2012 7:31am

I am getting something similar for what it's worth - but it's the DPMDB log file (not TEMPDB) that grows enormously.

My top tables are

TableName RowsK ReservedMB DataMB IndexSizeMB UnusedMB

tbl_TE_TaskTrail	1148	5382	4947	408	26
tbl_ARM_DirAndFile	21604	3209	3024	132	52
tbl_ARM_Path	1971	1644	779	717	147
tbl_RM_RecoverySource	282	1589	1452	105	30
tbl_JM_JobTrail	258	1120	1072	41	6
tbl_RM_SharePointRecoverableObject	439	953	314	622	16
tbl_JM_JobDefinition	33	601	599	0	1
tbl_RM_ReplicaTrail	608	514	387	47	78
tbl_RM_RecoverableObjectFileSpec	322	265	224	2	38
tbl_PRM_DatasetVolumesMap	261	187	167	4	15

Last night, starting at 11pm, I watched my DPMDB log file pass writes through at over 100 megabytes/second, until it consumed over 50gb, filled the disk and burst. This is on a 29gb data file and it consumed that 50gb in around 10-15 minutes.

Was also watching another server, that also had UR3 installed do exactly the same thing, but it only had 25gb of space to write the log to so it died earlier. Tonight, we're giving up considerably more space to the DPM logs to see where it goes.

I took a SQL Profiler trace watching the logs expand. It was horrific, adding another 500mb every few seconds. Tonight, I'll be watching it and tracing the actual SQL going on as well.

Doesn't seem to be sharepoint related for me, so posting this just in case it's relevant to others.


  • Edited by andreww Thursday, November 01, 2012 11:03 AM table formatting
November 1st, 2012 10:59am

We had a client with the same issue. We also called Microsoft and they gave as the same solution as "Ahmed Nabil Mahmoud Consulting" above.

Tomorrow we know if it worked.

  • Proposed as answer by PatLewis Thursday, December 06, 2012 5:38 PM
Free Windows Admin Tool Kit Click here and download it now
November 28th, 2012 1:42pm

If you are applying the script referenced in this thread there is an additional script that you need to execute after applying it.

This script will cause a new catalog check point to be synchronized with Sharepoint the next time the datasource is synchronized.

This is scheduled to be fixed in Update Rollup 4

USE [DPMDB]
GO
UPDATE tbl_PRM_DatasourceConfigInfo
SET ROCatalogCheckPoint = NULL
WHERE DatasourceId IN
(SELECT DISTINCT ReferentialDatasourceId FROM tbl_IM_ProtectedObject
WHERE ReferentialDatasourceId <> NULL)
GO

Thanks,

Patrick Lewis| patlewis@microsoft.com

Senior Escalation Engineer, System Center Global Escalation Services

December 6th, 2012 5:42pm

Please pay attention, I think this piece of code is incorrect. "<>" cannot be used with a NULL value. This SELECT DISTINCT statement returns no values at all. "<>" needs to be changed to "IS NOT".

USE [DPMDB]
GO
UPDATE tbl_PRM_DatasourceConfigInfo
SET ROCatalogCheckPoint = NULL
WHERE DatasourceId IN
(SELECT DISTINCT ReferentialDatasourceId FROM tbl_IM_ProtectedObject
WHERE ReferentialDatasourceId IS NOT NULL)
GO

  • Proposed as answer by Edgar Escobedo Thursday, June 06, 2013 1:07 PM
  • Unproposed as answer by Edgar Escobedo Thursday, June 06, 2013 1:07 PM
  • Proposed as answer by Edgar Escobedo Thursday, June 06, 2013 1:07 PM
Free Windows Admin Tool Kit Click here and download it now
April 24th, 2013 8:21am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics