none
DPM 2016 to 2019 upgrade (including Windows Server and SQL upgrade) RRS feed

  • Question

  • Hello all,


    I'm going to upgrade DPM from 2016 to 2019. I did some research and it looks like there will be a bit more work as I have to upgrade also OS  & SQL. Currently, the DPM is running on Windows Server 2012 Standard and SQL 2014.... Looks like both of them needs to be upgraded. There are just handful of servers that are running agent and are taking the backups from. Nothink complicated. Therefore I am trying to find out whether:

    • is in-place from Windows Server 2012 to 2019 a good way to go, or there would be troubles with it? It is a Hyper-V VM
    • upgrade from SQL 2014 to 2016 - are there any tricky parts?
    • upgrade from DPM 2016 to 2019 - are there any tricky parts?

    From what I've found from microsoft docs etc, it is quite straight forward but I am not sure whether it will not cause some mess to each other... I would like to keep as exisitng configuration as possible, including DPM jobs, etc.

    What is the best way to proceed? Frankly, I would prefere the upgrade instead of installing all from scratch, but not sure whether I could expect any troubles with it.

    I'm thinking of these two ways:

    Upgrade:

    1. take backups of DPM databases
    2. in-place upgrade of Windows from 2012 to 2019
    3. upgrade SQL from 2014 to 2016
    4. upgrade DPM from 2016 to 2019

    New installation:

    1. bring up a new VM with Win 2019
    2. install SQL 2016
    3. install DPM 2019 and restore DPM database from backup 




    • Edited by mSumo Tuesday, June 23, 2020 12:26 PM
    Tuesday, June 23, 2020 12:25 PM

Answers

  • DPM 2016 can be extended yes, of course you won't get the latest new features that have come in DPM 2019, but upgrading is not yet a must, and DPM 2016 provides support for many coming years (mainstream till 1/11/2022, and extended till 1/11/2027).

    I'm not sure about the key, but in general the System Center product keys are the same for all System Center products, might be better checking with a trained Microsoft licensing specialist to be safe.
    https://www.microsoft.com/licensing/servicecenter/Help/Contact.aspx


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by mSumo Tuesday, June 23, 2020 9:49 PM
    Tuesday, June 23, 2020 2:48 PM

All replies

  • Hi mSumo,

    If I were you, I would always go for a new installation. Reason being, if anything breaks during this process, you will still have your old servers/SQL/DPM instances untouched and you can always fall back. If you upgrade the existing configuration and if anything goes wrong, it would take huge amount of time to fix it and get the back up started.

    New Installation should go like below:

    • Bring up a new VM with Win 2019
    • install SQL Server 2014 SP2/Sp4.
    • install DPM 2016. It would be RITM.
    • Install the UR which was previously installed
    • Restore the DPMDB from previous DPM installation
    • Upgrade SQL 2014 to 2016
    • Upgrade DPM 2016 to DPM 2019

    Make sure you take a fresh DPMDB full backup after every stage so that you don't lose any data.

    Refer this link regarding DPM supported SQL versions and other OS requirements/Pre-requisites.

    Tuesday, June 23, 2020 12:55 PM
  • Hi,

    If you'll have to upgrade the Windows Server operating system version, as well as the SQL Server version, I would recommend a fresh install. Although it is fully supported to perform an in-place upgrade, but as you have quite many extra steps involved with the OS and SQL upgrade, the risks becomes higher.

    Either way, if you choose to go for the in-place upgrade, then it is fairly straight forward:

    1. In-place upgrade the Windows Server to at least 2016, preferably to 2019.
    (Upgrade Windows Server 2012 R2 to Windows Server 2019)

    2. In-place upgrade the SQL Server to at least 2016, preferably to 2017
    (Supported version & edition upgrades (SQL Server 2017)

    3. In-place upgrade DPM 2016 to 2019
    (Upgrading to DPM 2019 Step-by-Step)

    ---------------------------------------------------------------------------------------------

    If you want to use the existing DPM database, you will need to:

    1. Install a new Windows Server 2016/2019. (preferably 2019)

    2. Install the same SQL Server as was previously used (SQL Server 2014).

    3. Restore the DPM database.

    4. Install the same DPM version as was previously used (DPM 2016) and use the existing database.

    5. In-place upgrade the SQL Server to 2016/2017. (preferably 2017)

    6. In-place upgrade DPM 2016 to 2019.

    ---------------------------------------------------------------------------------------------

    If you want to start completely fresh:

    1. Install a new Windows Server 2016/2019 (preferably 2019)

    2. Install the new SQL Server 2016/2017 (preferably 2017).

    3. Install DPM 2019.

    4. Install DPM 2019 Update Rollup 1.

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, June 23, 2020 12:56 PM
  • well... the DPM2016 license is expiring by the end of this month, so there will not be any "fail back" if anything goes wrong :) ... I need to get to DPM2019 one way or another....

    anyway, thank you for your input. Will be handy if I go for fresh install...

    Tuesday, June 23, 2020 2:07 PM
  • What kind of license agreement do you have? Note that all System Center products use the same license key.

    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, June 23, 2020 2:12 PM
  • Hi Leon,

    let me provide few details about what is going on... 

    A client had a 3-year agreement (Open Value Agreement) for several System Center tools (DPM, SCCM, etc) which are expiring. As he wanted to keep using only DPM, he asked to re-new that one product only. So an order was placed and he can see DPM2019 in his Volume Licencing Portal and also the KEY for it. Now... as we've found out, it is a lot of hassle to upgrade DPM2016-2019 so trying to find a way how to perform it.... DPM 2019 is not a must, if we can extend 2016 with the same key?..., that would work as well. 


    • Edited by mSumo Tuesday, June 23, 2020 2:45 PM
    Tuesday, June 23, 2020 2:44 PM
  • DPM 2016 can be extended yes, of course you won't get the latest new features that have come in DPM 2019, but upgrading is not yet a must, and DPM 2016 provides support for many coming years (mainstream till 1/11/2022, and extended till 1/11/2027).

    I'm not sure about the key, but in general the System Center product keys are the same for all System Center products, might be better checking with a trained Microsoft licensing specialist to be safe.
    https://www.microsoft.com/licensing/servicecenter/Help/Contact.aspx


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by mSumo Tuesday, June 23, 2020 9:49 PM
    Tuesday, June 23, 2020 2:48 PM
  • great info... thanks a lot Leon. Appreciate your help... Will call MS Support tomorrow... 

    Would ask you just one more question about DPM 2016 if you don't mind? I was trying to find a place where I could put a licence key when I have it, or check when the license is expiring. However, I cannot find that info anywhere in that software. I was trying to google it but no luck. Is it even possible to find these in the software directly? 

    Tuesday, June 23, 2020 9:20 PM
  • Unfortunately the only time you can enter the product key for DPM is during the installation, it cannot be done afterwards. 

    So if your license is indeed expiring, then you will have to uninstall DPM (with the retain database option), then reinstall DPM and then enter your product key.

    I know it's a big flaw in the design, but the reinstall isn't a big deal in the end.

    (Please don't forget to mark any helpful reply as answer if you think they helped you, thank you!)


    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, June 23, 2020 9:23 PM