none
DPM 2016 - data transferred stuck after adding jobs to modern backup storage RRS feed

  • Question

  • Hi

    I upgraded DPM 2012 R2 according to https://docs.microsoft.com/en-us/system-center/dpm/upgrade-to-dpm-2016 , so far everything was fine until I added MBS and protection groups to it. At first it would allocate properly, but as soon as I added new members to it stuck for several minutes if not hours until the whole server started getting unresponsive.
    After cold boot everything looked fine but new jobs start to hang somewhat randomly at arbitrary "data transferred" values, no feedback, no error, no nothing.

    Is MBS the reason? Is there some known issue? In veeam forums I can read there an issue with 4k clusters on ReFS.

    Thanks


    • Edited by Marti__G Monday, August 7, 2017 4:50 PM
    Monday, August 7, 2017 4:48 PM

Answers

  • Update: After a reboot and remove of the MBS protection group DPM seems to work properly again.

    Conclusion: MBS is not usable at the moment.


    What confuses me is this note:

    https://docs.microsoft.com/en-us/system-center/dpm/prepare-environment-for-dpm


    Logical unit number (LUN)

    Applies only to DPM 2016 servers upgraded from DPM 2012 R2 that used legacy storage pool.
    Maximum of 17 TB for GUID partition table (GPT) dynamic disks
    2 TB for master boot record (MBR) disks
    Requirements are based on the maximum size of the hard disk that appears in the operating system.



    First of all dynamic disk are not support with MBS, and what about the 17TB limit? I could format a 37TB drive as MBS after all, just as basic disk...


    • Edited by Marti__G Tuesday, August 8, 2017 8:18 AM
    • Marked as answer by Marti__G Tuesday, August 8, 2017 8:18 AM
    Tuesday, August 8, 2017 8:18 AM

All replies

  • BTW: The ReFS issue I mentioned earlier: https://support.microsoft.com/en-us/help/4016173/fix-heavy-memory-usage-in-refs-on-windows-server-2016-and-windows-10
    Monday, August 7, 2017 6:37 PM
  • Update: After a reboot and remove of the MBS protection group DPM seems to work properly again.

    Conclusion: MBS is not usable at the moment.


    What confuses me is this note:

    https://docs.microsoft.com/en-us/system-center/dpm/prepare-environment-for-dpm


    Logical unit number (LUN)

    Applies only to DPM 2016 servers upgraded from DPM 2012 R2 that used legacy storage pool.
    Maximum of 17 TB for GUID partition table (GPT) dynamic disks
    2 TB for master boot record (MBR) disks
    Requirements are based on the maximum size of the hard disk that appears in the operating system.



    First of all dynamic disk are not support with MBS, and what about the 17TB limit? I could format a 37TB drive as MBS after all, just as basic disk...


    • Edited by Marti__G Tuesday, August 8, 2017 8:18 AM
    • Marked as answer by Marti__G Tuesday, August 8, 2017 8:18 AM
    Tuesday, August 8, 2017 8:18 AM