locked
Expired Recovery Points Not Being Removed Automatically - DPM 2012 SP1 RRS feed

  • Question

  • I have a DPM 2012 SP1 server, which was upgraded from DPM 2010 to DPM 2012 to DPM 2012 SP1.  Since the upgrade, expired recovery points are not being removed automatically.

    So in all my recovery groups, the retention is set to 7 days.  Today is 1/24, but all protected data have recovery points back to 1/11, which is 13 days.  I'm noticing that I'm running out of recovery volume space frequently.  I just started running pruneshadowcopies powershell script manually to hopefully free some space, but I need this to work correctly automatically.

    EDIT: I noticed this topic being discussed with both DPM 2007 and DPM 2010 and there were apparently hotfixes.  Just to be clear, this is DPM 2012 SP1 and what I've found for older version does not seem to help.

    Friday, January 24, 2014 11:48 PM

All replies

  • Hi,

    You can check to see that the pruneshadowcopiesDpm2010.ps1 was executed and it's exit code = 0.

    1) Open an administrative command prompt and CD to the DPM installation path\temp folder.
    2) Run the find command as follows.

         C:\Program Files\Microsoft DPM\DPM\Temp>find /i "prune" msdpm*.errlog

    It will list all the times that PruneshadowcopiesDpm2010.ps1 was initiated which should be at midnight GMT time.

    ---------- MSDPMCURR.ERRLOG
    0C38    120C    01/25   06:00:06.226    19      SummaryManagerMachine.cs(953)           054E3E2F-4AE0-4CE4-9774-907765C9E489    NORMAL  powershell process started with  file=C:\Windows\System32\Window
    sPowerShell\v1.0\powershell.exe args=-Command ". 'c:\Program Files\Microsoft DPM\DPM\bin\DpmCliInitScript.ps1'; . 'c:\Program Files\Microsoft DPM\DPM\bin\pruneshadowcopiesDpm2010.ps1'"
    0C38    1460    01/26   06:00:05.506    19      SummaryManagerMachine.cs(953)           29E4D618-97CC-40D7-AD54-7039A6184C00    NORMAL  powershell process started with  file=C:\Windows\System32\Window
    sPowerShell\v1.0\powershell.exe args=-Command ". 'c:\Program Files\Microsoft DPM\DPM\bin\DpmCliInitScript.ps1'; . 'c:\Program Files\Microsoft DPM\DPM\bin\pruneshadowcopiesDpm2010.ps1'"
    0A00    048C    01/27   06:00:05.471    19      SummaryManagerMachine.cs(953)           542C57EB-0081-4BA9-8C21-ABAF32B7D309    NORMAL  powershell process started with  file=C:\Windows\System32\Window
    sPowerShell\v1.0\powershell.exe args=-Command ". 'c:\Program Files\Microsoft DPM\DPM\bin\DpmCliInitScript.ps1'; . 'c:\Program Files\Microsoft DPM\DPM\bin\pruneshadowcopiesDpm2010.ps1'"


    3) Take one of the TASK GUIDS and search for that.


    C:\Program Files\Microsoft DPM\DPM\Temp>find /i "542C57EB-0081-4BA9-8C21-ABAF32B7D309" msdpm*.errlog >542C57EB-0081-4BA9-8C21-ABAF32B7D309.txt


    4) Open the results in notepad.

    C:\Program Files\Microsoft DPM\DPM\Temp>notepad 542C57EB-0081-4BA9-8C21-ABAF32B7D309.txt

    5) Search for pruneshadowcopiesDpm2010.ps1 and the next line will be when it completed and it's exit code.  In this case it exited with status 0 = no error and it took 1 minute 46 seconds to complete.


    You can see how long it ran and if precess exited without an error.

    0A00 048C 01/27 06:00:05.471 19 SummaryManagerMachine.cs(953)  542C57EB-0081-4BA9-8C21-ABAF32B7D309 NORMAL powershell process started with  file=C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe args=-Command ". 'c:\Program Files\Microsoft DPM\DPM\bin\DpmCliInitScript.ps1'; . 'c:\Program Files\Microsoft DPM\DPM\bin\pruneshadowcopiesDpm2010.ps1'"
    0A00 048C 01/27 06:01:46.895 19 SummaryManagerMachine.cs(974)  542C57EB-0081-4BA9-8C21-ABAF32B7D309 NORMAL powershell process exited with 0



    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.


    Monday, January 27, 2014 10:04 PM