none
Issue with Disk Management RRS feed

  • Question

  • Hi

    We are currently using DPM 2016  (1807) in our environment. We are having issues with one of our DPM server where the disk space is getting occupied more than the expected.
    For example:  If we assign 7 recovery points for a server in one protection group. It takes around 9-10 and the cleanup process isnt happening after 7 recovery points. Couldn't really get a clear overview of whats happening around ?

    Is there anyone who can help me with this?

    let me know if you want me to investigate some logs or perform some checks to get this tweaked. Thank you!!

    Monday, September 30, 2019 1:48 PM

All replies

  • Hi,

    Could you provide some screenshots of this behavior?

    Could you clarify a bit more on the following:
    "For example:  If we assign 7 recovery points for a server in one protection group. It takes around 9-10 and the cleanup process isnt happening after 7 recovery points."


    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, September 30, 2019 2:14 PM
  • Hi Leon

    Here is what i am talking about.
    I have set the retention period as 7 days for one protection group.

    (Below is the Gdrive link as i am not able to attach the images as i am new to the forums and created my profile today) . you may find the images related to this in the drive below. Please check .

    https://drive.google.com/open?id=13wHzh2BnbW-cZI2dIUysrquhAeaUad9E

    As per the DPM structure i believe if we set the retention period as 7 days. Then it should just keep the recovery points for those 7 days and clean up the every other 8 recovery point . which is not happening in my case.

    Let me know if you need any further more details on this.

    Monday, September 30, 2019 3:45 PM
  • It's likely that the pruning job has not run at all or not run successfully, and therefore you may have more recovery points than you should.

    Every day at midnight DPM will launch a powershell script called pruneshadowcopiesDpm.ps1 that will update the replica with the earliest recovery point located in the recovery point volume of the DPM server, but this happens only if the retention time is expired.

    You can run this manually, but I would recommend to run it when no backup jobs are running.

    The script is located here:

    • C:\Program Files\Microsoft System Center\DPM\DPM\bin

    You will need to have access with the user you're running the script with to the DPM storage volume (you can take ownership of the volume and then add access to yourself), or you can use PSExec to run the pruneshadowcopiesDpm.ps1 as the local SYSTEM user (see: Error running PruneShadowCopies on DPM 2016).


    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, September 30, 2019 5:01 PM
  • I ran the script . It gave me the error as mentioned in the Error URL and followed the steps.

    Finally it ran successfully (without any errors).

    Unfortuantely, still the issue isnt resolved.
    I still see the recovery points are not cleared. They are still the same. Is there anything else, i need to verify?

    Or do i need to wait for some more time on this.

    Tuesday, October 1, 2019 12:44 PM
  • If a recovery point has for example been created manually, you will then see more recovery points than you "should", so it doesn't have to be something alarming.

    Has the number of recovery points grown bigger or is the difference as of today still the same?

    Eventually the recovery points should get cleared when DPM automatically does its cleaning job at midnight.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, October 1, 2019 12:49 PM
  • Its same as of now. 
    Will wait today and let you know if i see any difference tomorrow
    Tuesday, October 1, 2019 3:24 PM
  • Just checking to see if you have any update?

    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, October 3, 2019 9:51 AM
  • Sorry for the late response.

    Unfortunately that didn't fix the issue.
    Is there anything else we need to check?
    Thursday, October 10, 2019 1:17 PM
  • As mentioned earlier, the retention period (in days) does not necessarily have to be the same as the amount of recovery points.

    If you have manually created one or more recovery points and they are within the retention period, then these will not be pruned by DPM and it will show that you have more recovery points than retention days.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, October 10, 2019 1:53 PM
  • I haven't created any manual recovery point FYI.
    However, the issue seems to be weird just with this server. Rest all server in my environment works great.

    it just works the way as per retention period set.
    Where do we generally get an idea about the amount of recovery points that are set for a Protection group. As far as i am aware, the retention period which was set will help us understand. Let me know if we can know in any other way
    Thursday, October 10, 2019 3:40 PM
  • If the recovery points were not created manually, then I can't tell why it's showing like that.

    The only places where you will see the amount of recovery points available is in the console, PowerShell or in the DPM reports.

    You could check if the guide below still works for DPM 1807 to remove the unnecessary recovery points:
    DPM 2012 R2: Remove Recovery Points

    Downloadable script:
    DPM 2012 R2: Remove Recovery Points - version 2


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, October 10, 2019 5:48 PM