none
DPM 2012 R2 Disk Allocation shows 0GB for Data Size RRS feed

  • Question

  • Hi All

    DPM 2012 R2 (unsure which roll up at this moment as away from office)

    Noticed that an old Protection Group backing up VM's in Hyper-V is showing 0GB data size for each protected VM in the PG.

    There's around 8 VM's in the PG which are RDS servers. The VM's themselves arent particularly large.

    Also the stated Replica Volume size for a couple of the VM's in the PG is showing well over 1TB. The VM's themselves are maybe 100GB maximum size.

    Retention to disk is only 10 days with 1 recovery point per day

    I know that no one has edited the disk allocation manually so wondered if this is a common occurrence or what would have caused this to happen on the DPM server?

    Does the fact the data size show 0GB mean the recovery points are likely to be useless?

    Many thanks 

    Thursday, January 9, 2020 8:52 PM

All replies

  • Hi,

    There were a known issue regarding the display of the recovery point size in early DPM 2012 R2 versions, let us know which Update Rollup level you're running on.

    I would highly recommend updating to the latest Update Rollup if you haven't already:

    Update Rollup 14 for System Center 2012 R2 Data Protection Manager.

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Friday, January 10, 2020 8:44 AM
  • Hi,

    There were a known issue regarding the display of the recovery point size in early DPM 2012 R2 versions, let us know which Update Rollup level you're running on.

    I would highly recommend updating to the latest Update Rollup if you haven't already:

    Update Rollup 14 for System Center 2012 R2 Data Protection Manager.

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Hi Leon,

    Version 4.2.1603.0 - which i believe is RU14

    I've just tried to modify Disk Allocation for the PG to try and shrink one of the Replica Volumes but was hit with an error ID 32070

    Windows cannot shrink currently due to the presence of data towards the end of the volume

    Disk Allocation screen shot

    Friday, January 10, 2020 10:46 AM
  • Here's a similar thread with the error you're receiving:
    Can not shrink DPM allocated volume

    As for the "0GB" issue did you try by simply rebooting the DPM server?


    Blog: https://thesystemcenterblog.com LinkedIn:

    Friday, January 10, 2020 11:33 AM
  • Here's a similar thread with the error you're receiving:
    Can not shrink DPM allocated volume

    As for the "0GB" issue did you try by simply rebooting the DPM server?


    Blog: https://thesystemcenterblog.com LinkedIn:

    Yes the DPM server has been rebooted at least 3 or 4 times.

    It appears Protection Groups that show 0GB for Disk Allocation are all the Hyper-V Level Protection Groups - so backing up VM level.

    The Protection Groups that are backing up at Volume and SQL level appear to be able to show Data Size.

    Also this DPM server is unable to calculate the Total data size and the Disk space allocated in DPM when creating a new Protection Group.

    The Review Disk Allocation step in the Create New Protection Group Wizard sits there trying to calculate Total Data Size and Disk Space Allocation so unable to proceed to create the new PG.

    We have the DPM Database backed up to another DPM server. 
    At this stage is it sounding like a DB restoration is required?

    Monday, January 20, 2020 12:19 PM
  • This is a strange behaviour indeed, out of interest could you try protecting a single VM in a separate protection group and check if the result is the same?

    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, January 20, 2020 1:00 PM
  • This is a strange behaviour indeed, out of interest could you try protecting a single VM in a separate protection group and check if the result is the same?

    Blog: https://thesystemcenterblog.com LinkedIn:

    The only way i managed to try what you described above was to stop protection on a non-critical VM from one of the PG's, delete it from disk, then created a new PG with just that VM protected.

    The new PG created OK, however i get persistent Replica Inconsistent errors for that member and when trying to Modify Disk Allocation, this VM also shows 0GB for Data 


    Monday, January 20, 2020 1:09 PM