none
SCDPM 2016 - How to make existing storage pool a ReFS volume storage pool. RRS feed

  • Question

  • So we are planning to upgrade one of our DPM with below details :

    1 Windows Server 2012 R2, Standard -- In-Place upgrade to Windows Server 2016, Standard.

    2. SCDPM 2012 R2                            -- Upgrade to SCDPM 2016 and then to 1807 later.

    Since this is in place upgrade and we are not doing fresh install of DPM, we are upgrading DPM as well. Current storage pool is exposed and added as multiple disks to DPM. Is there any way to achieve using ReFS for this storage pool without loosing data ? 


    Friday, February 15, 2019 4:39 PM

Answers

  • You will not be able to "convert" your existing disks to MBS (ReFS) disks.

    When you upgrade to DPM2016 your current disks will still be the same as they were in DPM 2012 R2, so you will have to do as follows:

    1. Add new modern storage volume(s) to the DPM storage pool.

    2. Stop protection of the data sources you want to migrate and retain the data.

    3. Re-protect the data sources and select the modern storage volumes to use for protection.

    4. DPM will now copy the replica data from the old storage to the new modern storage replica.

    When the old recovery points expire on the legacy storage, the replica and recovery point volumes will get deleted. 


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by V Jay Rana Monday, February 18, 2019 12:19 PM
    Monday, February 18, 2019 9:53 AM
  • Yes I believe you can enable data deduplicaiton later on.

    Note that data deduplication on ReFS volumes only work on Windows Server version 1709 and later.

    https://docs.microsoft.com/en-us/windows-server/storage/refs/refs-overview


    Blog: https://thesystemcenterblog.com LinkedIn:


    • Edited by Leon Laude Tuesday, February 26, 2019 2:42 PM
    • Marked as answer by V Jay Rana Tuesday, February 26, 2019 3:46 PM
    Tuesday, February 26, 2019 2:40 PM
  • DPM is smart enough, you can continue using your DPM 2012 R2 disks with DPM 2016, they will not go offline or be reformatted.

    Remember, once you have upgraded to DPM 2016, only the new data sources will use Modern Backup Storage (MBS).


    On a side note, DPM 2019 is coming out within this month, it might also be worth considering.
    But I would still recommend taking this in small steps, so first of all DPM 2012 R2 -> DPM 2016.


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by V Jay Rana Monday, March 11, 2019 11:50 PM
    Monday, March 11, 2019 11:44 PM

All replies

  • Hello!

    You can also upgrade to DPM 1801 from either DPM 2012 R2 Update Rollup 14 (UR14), or from DPM 2016 Update Rollup 4 (UR4), and then upgrade from DPM 1801 to 1807 if you like.

    The most important thing when performing any kind of change as in a upgrade, make sure you do backups.
    With DPM, the DPM database is the crucial part and needs to be backed up.

    If you do choose to upgrade from DPM 2012 R2 to DPM 2016 you can update your existing protection groups to the new DPM 2016 features. 

    By default the protection groups are not changed, they will continue to function as they were configured in DPM 2012 R2.

    Updating the protection groups to use Modern Backup Storage is optional.

    To update the protection group, stop protection of all data sources with Retain Data, and add the data sources to a new protection group. DPM begins protecting these data sources the new way.

    Hope this helps!

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Friday, February 15, 2019 5:41 PM
  • Hi Leon

    Thanks for suggestion. 

    I am more concerned about the point "Updating the protection groups to use Modern Backup Storage is optional."

    Yes, I will ensure DPM database backup before upgrading. But as I said, with current storage pool layout we have added disks directly from DPM console, as Modern Backup Storage feature requires Basic disk to be formatted as simple volume (with ReFS), how we can convert existing storage pool to use MBS without loosing/moving protection group's data. 

    Monday, February 18, 2019 8:53 AM
  • You will not be able to "convert" your existing disks to MBS (ReFS) disks.

    When you upgrade to DPM2016 your current disks will still be the same as they were in DPM 2012 R2, so you will have to do as follows:

    1. Add new modern storage volume(s) to the DPM storage pool.

    2. Stop protection of the data sources you want to migrate and retain the data.

    3. Re-protect the data sources and select the modern storage volumes to use for protection.

    4. DPM will now copy the replica data from the old storage to the new modern storage replica.

    When the old recovery points expire on the legacy storage, the replica and recovery point volumes will get deleted. 


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by V Jay Rana Monday, February 18, 2019 12:19 PM
    Monday, February 18, 2019 9:53 AM
  • Thanks. I will do those steps. 
    Monday, February 18, 2019 12:20 PM
  • Just another one little query - Can we enable Deduplication on a RefS volume already added to DPM storage pool ? I got this skipped enabling before adding to DPM storage pool. I hope this will not impact any data residing on Refs storage pool volume. 
    • Edited by V Jay Rana Tuesday, February 26, 2019 2:23 PM
    Tuesday, February 26, 2019 2:18 PM
  • Yes I believe you can enable data deduplicaiton later on.

    Note that data deduplication on ReFS volumes only work on Windows Server version 1709 and later.

    https://docs.microsoft.com/en-us/windows-server/storage/refs/refs-overview


    Blog: https://thesystemcenterblog.com LinkedIn:


    • Edited by Leon Laude Tuesday, February 26, 2019 2:42 PM
    • Marked as answer by V Jay Rana Tuesday, February 26, 2019 3:46 PM
    Tuesday, February 26, 2019 2:40 PM
  • Thanks. I will enable it and verify if it's working fine.

    We have all 2016 servers with version 1607, but still getting Deduplication option


    • Edited by V Jay Rana Tuesday, February 26, 2019 3:46 PM
    Tuesday, February 26, 2019 3:43 PM
  • I got your point now Leon. I am getting option for Data Deduplication on Windows version 1607 but only for NTFS volumes, its grayed out for ReFS volumes. Since version 1709 is core server version, can we expect MS to support this feature on existing versions of Windows Server 2016 in future !! 

    I can see all version between 1709 and Windows Server 2019 are not with GUI.


    • Edited by V Jay Rana Thursday, February 28, 2019 2:33 PM
    Thursday, February 28, 2019 2:29 PM
  • There's been a lot of talks about this, there is a feedback about this in the link below, you may go and vote for it and hope that Microsoft will make support for data deduplication on ReFS on WIndows Server 2016 version 1607.

    https://windowsserver.uservoice.com/forums/295056-storage/suggestions/7962813-support-deduplication-on-refs?page=1&per_page=20


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, February 28, 2019 2:57 PM
  • Thanks a lot for clarification. Yes, voted. 
    Thursday, February 28, 2019 3:09 PM
  • >>When you upgrade to DPM2016 your current disks will still be the same as they were in DPM 2012 R2, so you will have to do as follows:

    Just about a last query, If we don't want to opt MBS..existing stoareg pool and configuration would work with DPM 1807??. We aren't getting new storage as fast as much I wan't to upgrade this DPM to latest so all DPM are on same version of SCDPM and Windows OS. 


    • Edited by V Jay Rana Monday, March 11, 2019 4:05 PM
    Monday, March 11, 2019 4:05 PM
  • MBS is enabled automatically when you're running at least DPM 2016 on Windows Server 2016.

    If DPM is running on a version of Windows Server older than Windows Server 2016, it doesn't use MBS.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, March 11, 2019 6:43 PM
  • Hi Leon 

    My major concern is, I don't have new storage now which I can add as ReFS, So I don't wan't to use MBS. But I wan't DPM and Windows to be upgraded from 2012 to 2016 (both). So, If I proceed with this, I am worry if existing volumes will offline or inactive ?? As you said 2016 will start MBS by default so I am worry how it DPM will handle old volumes (with existing data) when it not find ReFS. 

    Should I wait to proceed until I don't have storage to meet MBS requirements ?

    Or will it use existing NTFS ?
    • Edited by V Jay Rana Monday, March 11, 2019 9:02 PM
    Monday, March 11, 2019 8:59 PM
  • DPM is smart enough, you can continue using your DPM 2012 R2 disks with DPM 2016, they will not go offline or be reformatted.

    Remember, once you have upgraded to DPM 2016, only the new data sources will use Modern Backup Storage (MBS).


    On a side note, DPM 2019 is coming out within this month, it might also be worth considering.
    But I would still recommend taking this in small steps, so first of all DPM 2012 R2 -> DPM 2016.


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by V Jay Rana Monday, March 11, 2019 11:50 PM
    Monday, March 11, 2019 11:44 PM