none
New physical DPM host and migration plan RRS feed

  • Question

  • Hi guys, posting to get some input from some DPM experts here with regards to my rebuild and migration plan

    Our current set up is as follows:

    • Primary, Physical host, DAS, DPM 2016, Windows Server 2012R2
    • Secondary, Physical host, DAS, DPM 2016, Windows Server 2012R2

    We are looking to replace this set up with a new physical host running DPM 2019 on Windows Server 2019 as our primary and utilise Azure Backup getting rid of the secondary.

    Question: As it is not possible to bring over the existing storage pool to the new host, is there any benefit in retaining and upgrading the existing DPM database as opposed to starting with a fresh new one? I am not worried about having to reconfigure protection groups.

    The plan is to build the new primary and have it ready. Then migrate protection of selected protected servers over to the new DPM and into Azure by way of the following steps:

    1. Stop protection in existing DPM (keeping replica on disk)
    2. SetDPMServer.exe -dpmservername $newdpmserver on protected server
    3. Attach-ProductionServer.ps1 on new DPM console
    4. Upgrade agent on protected server from new DPM console
    5. Wait for replica rebuild on new storage pool
    6. Wait for full sync to Azure Backup

    Our internet bandwidth is limited to 500mbps (realistically can only probably use 200) and it would take days to seed our 20TB up to Azure. My thought process is that keeping both environments live and staggering the migration will minimise the risk of not having a off site back up.

    Keen to get any input - thanks.

    • Changed type hbza1 Tuesday, January 21, 2020 10:24 PM
    Tuesday, January 21, 2020 8:42 PM

Answers

  • Hi,

    Upgrading your existing environment would require a few extra steps, so it would be a lot easier to simply set up a new environment (DPM 2019 running on Windows Server 2019).

    The steps you have outlined are correct, as there is no other way of "moving/migrating" the protection groups or protected data sources.

    Question: As it is not possible to bring over the existing storage pool to the new host, is there any benefit in retaining and upgrading the existing DPM database as opposed to starting with a fresh new one? I am not worried about having to reconfigure protection groups.

    >> The only benefit is to keep old backups left of your environment, one thing you can do is to keep your current DPM 2016 environment as it is for a while (a few weeks to a few months), install a new DPM 2019 environment on the side and start moving all agents from the DPM 2016 -> DPM 2019 environment and start backing up everything in the new DPM environment. Once you have enough retentions in your new DPM 2019 environment, you can simply shut down and uninstall the older DPM 2016 environment.

    Starting fresh is usually a recommended approach, since your current DPM 2016 environment is running on Windows Server 2012 R2, it is not gaining benefit from the new Modern Backup Storage (MBS) feature that is introduced in DPM 2016 & DPM 2019. This is one reason to start fresh so that you can create new volumes that can benefit from the MBS feature.

    PS: Since this is a question, would you please mind changing the thread type to a Question type? Thanks!

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by hbza1 Tuesday, January 21, 2020 10:24 PM
    Tuesday, January 21, 2020 9:04 PM

All replies

  • Hi,

    Upgrading your existing environment would require a few extra steps, so it would be a lot easier to simply set up a new environment (DPM 2019 running on Windows Server 2019).

    The steps you have outlined are correct, as there is no other way of "moving/migrating" the protection groups or protected data sources.

    Question: As it is not possible to bring over the existing storage pool to the new host, is there any benefit in retaining and upgrading the existing DPM database as opposed to starting with a fresh new one? I am not worried about having to reconfigure protection groups.

    >> The only benefit is to keep old backups left of your environment, one thing you can do is to keep your current DPM 2016 environment as it is for a while (a few weeks to a few months), install a new DPM 2019 environment on the side and start moving all agents from the DPM 2016 -> DPM 2019 environment and start backing up everything in the new DPM environment. Once you have enough retentions in your new DPM 2019 environment, you can simply shut down and uninstall the older DPM 2016 environment.

    Starting fresh is usually a recommended approach, since your current DPM 2016 environment is running on Windows Server 2012 R2, it is not gaining benefit from the new Modern Backup Storage (MBS) feature that is introduced in DPM 2016 & DPM 2019. This is one reason to start fresh so that you can create new volumes that can benefit from the MBS feature.

    PS: Since this is a question, would you please mind changing the thread type to a Question type? Thanks!

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by hbza1 Tuesday, January 21, 2020 10:24 PM
    Tuesday, January 21, 2020 9:04 PM
  • Thank you Leon for you fast reply. Very appreciated. I will start fresh with a new DB and keep old environment around. 
    Tuesday, January 21, 2020 10:27 PM