DPMDB Log file is not truncating from backup by 2nd DPM server RRS feed

  • Question

  • I have 2 sites each with its own DPM2010 server. Each server is responsible to back up data at its respective location. Additionally, We have the SQL databases of each DPM server backed up by the other DPM server at the alternate site.

    DPM1 is in the office & DPM2 is at the alternate site.

    DPM1 SQL Databases are having problems due to the log files from the DPMDB, msdb, ReportServer$MSDPM2010, & ReportServer$MSDPM2010TempDB databases. For example the MSDPM2010_log.ldf file size is 76 GB. the hard disk ran out of space until I could free up about 12 GB.  In the SSMS I ran the query, : Select name, log_reuse_wait_desc from sys.databases. The results are LOG_BACKUP for the databases mentioned above. I go to DPM2 and run a "Perform Consistency Check" on these databases followed by "create a recovery point" thinking these actions will truncate the log files after backing up the DPM1 databases. Nothing changes.

    Additionally, the Tape jobs that were supposed to run over the last weekend did not run. They do not appear in the failed alerts section of the Monitioring Tab. According to the DPM1 application, its like these tape backup jobs were not supposed to happen.

    Please help.

    Monday, October 8, 2012 8:54 PM


All replies

  • Remember : the DPMDB is in simple recovery model , so you can not truncate the log by running inc. Backup , try to use
    DBCC SHRINKFILE , this is the syntax for the command


    Islam Gomaa Microsoft MVP | System Center Data Protection Manager email: Islam @ Islam Blog: Website:

    Tuesday, October 9, 2012 6:17 AM
  • Unfortunately, I set the DPMDB to FULL recovery model and used the dpm2 protection group to back up the database on an hourly basis.

    I have switched it back to simple recovery but I fear too much damage has been done. tape jobs that have worked for months without isue have stopped working properly. The change from the default recovery to full recovery mode was made several months back as well - I'm curious as to why this has not caused more issue until now.

    Can you provide me with the default recovery modes for the msdb, ReportServer$MSDPM2010, & ReportServer$MSDPM2010TempDB databases? I'm guessing simple as well.


    Tuesday, October 9, 2012 1:43 PM
  • Yes , they are Simple Mode

    Islam Gomaa Microsoft MVP | System Center Data Protection Manager email: Islam @ Islam Blog: Website:

    Tuesday, October 16, 2012 2:01 AM
  • Hi Guys

    I'm getting the same thing - I have two sites that back up each other's DPM databases. To try and keep on top of the transaction log, I'm also running them in Full Recovery with 15 minute syncs.

    However, at night, the transaction logs on these servers go through the roof - it appears some scheduled job is making the t-log grow to more than three times the size of the database. This has only happened recently however (or has only happened recently enough to fill the disk and become an issue - perhaps we just never noticed before).

    Is such spectacular logfile growth for DPM2012DB normal? Any suggestions what we can do about this? I've set the growth factor to be 100mb instead of the default 10%, as of course as the log files increase, they will subsequently increase exponentially in size probably taking far more than they'll need (it was observed that the last expansion was almost 5gb).

    Thanks for any assistance.

    Monday, October 29, 2012 11:42 AM
  • Which patch level do you have installed? with DPM 2012 UR3, this is a known issue when protecting sharepoint; we suffered this daily enormous growth of the DPM database (mdf+ldf arrived to >130Gb, and total data was no more than 9Gb).

    Are the logs full or you can shrink the database?

    Tuesday, November 6, 2012 8:04 AM
  • In my case, we applied the fix for UR3 regarding sharepoint and got it back down to a normal size with a standard shrink.
    Tuesday, November 6, 2012 9:56 AM
  • Hi Andreww,

    DPM 2012 RU3 has introduced a spelling mistake in SQL Store Procedure leading to dysfonction of Sharepoint Catalog task.

    I wrote a post on this issue :

    You may also applied SP1 beta to fix it.


    Please remember to click “Mark as Answer” on the post that helps you. This posting is provided "AS IS" with no warranties. knowledge is valid only if it is shared by All.

    My DPM blog Yet Another DPM Blog

    Tuesday, November 13, 2012 9:09 AM
  • I use SQL script in FULL recovery model for DPMDB

    BACKUP LOG DPMDB TO DISK = N'D:\Backup\DPMDB_log.bak'


    It helped me!

    Have a nice day !!! DPM 2012 R2: Remove Recovery Points

    Tuesday, March 10, 2015 11:56 AM