none
Upgrade Windows Server AND DPM from 2016 to 2019? RRS feed

  • Question

  • I have a Windows Server 2016 virtual machine running in a Windows Server 2016 HyperV cluster. In the virtual machine I am running DPM 2016 with a local SQL Server 2014.

    The storage pool is in a separate vhdx file mounted to the virtual machine and uses Modern Backup Storage.

    There is a fairly straight forward process for upgrading DPM in place from 2016 to 2019 and also for moving the DPM Database to a new SQL Server 2017 instance first.

    But I also need to upgrade the OS in the virtual machine to Windows Server 2019.

    Could I do one of these:

    1. Perform an in-place upgrade of Windows AFTER upgrading DPM? Will DPM 2019 "survive" that?
    2. Perform an in-place upgrade of Windows BEFORE upgrading DPM? Will DPM 2016 "survive" that? I doubt it. Is Windows Server 2019 even a supported OS for DPM 2016??
    3. Do a fresh install of Windows Server 2019 and SQL Server 2017, move the DPM database, mount the storage pool vhdx, do a fresh install of DPM 2019 and point it to the restored database and mounted pool?? Is there a recipe for this somewhere??

    Thanks for any input.

    Saturday, May 25, 2019 5:42 PM

Answers

  • Hello Thomas,

    In general it is always recommended to perform a clean install, I would also personally recommend installing a fresh Windows Server 2019 on the side and move the DPM database, install DPM 2016 and finally upgrade DPM to 2019.

    While upgrading an operating system is supported, it can have side effects, and everyone rather want to start from a clean slate.

    So here's the procedure you would follow:

    1. Stop all the DPM jobs.

    2. Backup the DPM database.

    3. Uninstall DPM.

    4. Shut down the old DPM server.

    5. Reset/remove the old DPM server AD computer account.

    6. Install the new server and us ethe same name and IP as the old DPM server.

    7. Restore the DPM database on the new server.

    8. Attach the DPM's storage pool disks.

    9. Reinstall DPM 2016 and select existing DPM database.

    10. Run the following command:

    DPMSync -Sync

    11. Perform consistency checks.

    12. Upgrade DPM to 2019 (you can follow the guide or HERE).


    I have also written a step-by-step guide on how to upgrade to DPM 2019:

    Upgrading to DPM 2019 Step-by-Step
    https://thesystemcenterblog.com/2019/03/17/upgrading-to-dpm-2019-step-by-step

    or you can find the same guide on the TechNet Wiki:

    https://social.technet.microsoft.com/wiki/contents/articles/52731.upgrading-to-dpm-2019-step-by-step.aspx

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:


    • Edited by Leon Laude Saturday, May 25, 2019 6:42 PM edited numbering
    • Marked as answer by ThomasIsr Saturday, May 25, 2019 7:47 PM
    Saturday, May 25, 2019 6:08 PM
  • Yes. I plan to follow your steps except for your steps 3 and 9. So like this:

    1. Stop all the DPM jobs.

    2. Backup the DPM database.

    3. Shut down the old DPM server.

    4. Reset the old DPM server AD computer account.

    5. Install the new server and use the same name and IP as the old DPM server.

    6. Restore the DPM database on the new server.

    7. Attach the DPM's storage pool disks.

    8. Run the following command: DPMSync -Sync

    9. Perform consistency checks.

    10. Install DPM 2019 and select existing DPM database.

    • Marked as answer by ThomasIsr Saturday, May 25, 2019 7:48 PM
    Saturday, May 25, 2019 7:35 PM

All replies

  • Hello Thomas,

    In general it is always recommended to perform a clean install, I would also personally recommend installing a fresh Windows Server 2019 on the side and move the DPM database, install DPM 2016 and finally upgrade DPM to 2019.

    While upgrading an operating system is supported, it can have side effects, and everyone rather want to start from a clean slate.

    So here's the procedure you would follow:

    1. Stop all the DPM jobs.

    2. Backup the DPM database.

    3. Uninstall DPM.

    4. Shut down the old DPM server.

    5. Reset/remove the old DPM server AD computer account.

    6. Install the new server and us ethe same name and IP as the old DPM server.

    7. Restore the DPM database on the new server.

    8. Attach the DPM's storage pool disks.

    9. Reinstall DPM 2016 and select existing DPM database.

    10. Run the following command:

    DPMSync -Sync

    11. Perform consistency checks.

    12. Upgrade DPM to 2019 (you can follow the guide or HERE).


    I have also written a step-by-step guide on how to upgrade to DPM 2019:

    Upgrading to DPM 2019 Step-by-Step
    https://thesystemcenterblog.com/2019/03/17/upgrading-to-dpm-2019-step-by-step

    or you can find the same guide on the TechNet Wiki:

    https://social.technet.microsoft.com/wiki/contents/articles/52731.upgrading-to-dpm-2019-step-by-step.aspx

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:


    • Edited by Leon Laude Saturday, May 25, 2019 6:42 PM edited numbering
    • Marked as answer by ThomasIsr Saturday, May 25, 2019 7:47 PM
    Saturday, May 25, 2019 6:08 PM
  • Hello Leon

    Thank you for a very quick reply!

    A few questions:

    You say that "upgrading an operating system is supported". Does that mean that both of my options 1 and 2 are supported? Are you aware of any statements to this effect from official Microsoft sources?

    Similarly: Is your 12 step procedure for a clean install based on Microsoft sources?

    And for the specific steps:

    Consider renumbering them :-)

    Why is step 3 (Uninstall DPM) needed? I will just delete the vm once the new one is working.

    What is the difference between Reset and Remove in step 5 (Reset/remove the old DPM server AD computer account)?

    Why do I need step 9 (Reinstall DPM 2016 and select existing DPM database)? Can I not go straight to DPM 2019?

    And thanks for the guide on your blog/TechNet. I had actually just read that before posting.

    Thomas

    Saturday, May 25, 2019 6:30 PM
  • Yes, upgrading Windows Server 2016 to Windows Server 2019 is officially supported by Microsoft, but not "recommended".

    Here are the official documentations:

    Upgrade Windows Server 2016 to Windows Server 2019
    https://www.microsoft.com/upgradecenter/scenario/WS2016-on-prem-to-WS2019

    Install | Upgrade | Migrate to Windows Server 2019
    https://docs.microsoft.com/en-us/windows-server/get-started-19/install-upgrade-migrate-19

    You can just power down the VM if you want, just make sure to stop all DPM jobs, DPM services and then shut down the DPM server.

    Resetting the AD computer account makes you able to simply re-use the same AD-account (if you're afraid of deleting it).

    DPM 2016 and DPM 2019 have some differences, so you can't simply install a newer DPM and use an older database, it will cause issues.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Saturday, May 25, 2019 6:47 PM
  • Yes. I know that upgrading Windows 2016->2019 is supported in general, but is it specifically supported for a DPM workload? The Windows docs are very general/anecdotal about upgrading and never discsus anything other than settings, server roles and data. I am very skeptical that it would work.

    You say: "... so you can't simply install a newer DPM and use an older database, it will cause issues.". But that is precisely what you do in your step 12. Installing DPM 2019 on top of 2016 upgrades the 2016 database.

    Saturday, May 25, 2019 7:00 PM
  • It does not say about the workloads, as there can be thousands, I have performed an in-place upgrade of a Windows Server on a DPM server, it worked but there were some minor issues, so I would avoid it if possible.

    It's not entirely the same, when you upgrade DPM from the installation media it will add/modify registry entries and do some changes in the database as well, this way you ensure that everything gets done in a clean and supported way.

    I'm not even sure if DPM 2019 will work if you simply attach a DPM 2016 database.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Saturday, May 25, 2019 7:11 PM
  • Thanks. I will avoid the in place upgrade of Windows.

    And to be completely clear:

    I am not proposing to install DPM 2019 and then attach a DM 2016 database. I am certain that would fail.

    I was suggesting to build the new Windows 2019 server, install SQL Server 2017, move the DPM database over, attach the pool vhdx and the run the DPM 2019 install. Here I would assume that I would get this option:

    From your own guide. And that the DPM 2019 installer would correctly upgrade the database.


    • Edited by ThomasIsr Saturday, May 25, 2019 7:26 PM
    Saturday, May 25, 2019 7:24 PM
  • Yes that sounds good :-)

    And as the warning in the screenshot says, take a backup of the DPM database before anything, and you should be good to go!


    Blog: https://thesystemcenterblog.com LinkedIn:

    Saturday, May 25, 2019 7:28 PM
  • Yes. I plan to follow your steps except for your steps 3 and 9. So like this:

    1. Stop all the DPM jobs.

    2. Backup the DPM database.

    3. Shut down the old DPM server.

    4. Reset the old DPM server AD computer account.

    5. Install the new server and use the same name and IP as the old DPM server.

    6. Restore the DPM database on the new server.

    7. Attach the DPM's storage pool disks.

    8. Run the following command: DPMSync -Sync

    9. Perform consistency checks.

    10. Install DPM 2019 and select existing DPM database.

    • Marked as answer by ThomasIsr Saturday, May 25, 2019 7:48 PM
    Saturday, May 25, 2019 7:35 PM
  • Sounds good.

    Blog: https://thesystemcenterblog.com LinkedIn:

    Saturday, May 25, 2019 7:46 PM