none
Upgrade DPM 1807 to DPM 2019

All replies

  • 1. Are there any limitations when running DPM 2019 on Windows Server 2016 and NOT Windows Server 2019?

    As far as I know there are not limitations running DPM 2019 on Windows Server 2016. 

    2. Is it supported to run DPM 2019 on SQL 2014SP2 Database?

    For DPM 2019 you will need to use SQL Server 2016 or 2017.


    Microsoft Certified Professional

    [If a post helps to resolve your issue, please click the "Mark as Answer" of that post or click Answered "Vote as helpful" button of that post. By marking a post as Answered or Helpful, you help others find the answer faster. ]

    Thursday, May 9, 2019 12:51 PM
  • Hi,

    1. Are there any limitations when running DPM 2019 on Windows Server 2016 and NOT Windows Server 2019?

    Answer: There are no limitations.

    2. Is it supported to run DPM 2019 on SQL 2014SP2 Database?

    Answer: DPM 2019 currently supports SQL Server 2016 and Service Packs, and SQL Server 2017.

    So while upgrading DPM to 2019, you can upgrade the SQL Server at the same time, you can refer to the link below:

    Migrate the DPM database during upgrade
    https://docs.microsoft.com/en-us/system-center/dpm/upgrade-dpm?view=sc-dpm-2019#migrate-the-dpm-database-during-upgrade

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, May 9, 2019 2:28 PM
  • Hi,

    thanks for the answer.
    We tried this but it did not work because of MS SQL Reporting Services.

    The article does not say anything about Reporting Services.

    We tried:
    - Migration of Reporting Services to 2017 before the upgrade

    - Usage of of a new Reporting Services DB

    - Changing SSL and certificate settings (Port 443 etc.)

    No matter what we tried DPM Upgrade always stops because of Reporting Services and in the DPMSetup.log we can see a dependancy to the "old" Reporting Services - so the setup tries to access those.

    kind regards

    /bkpfast


    My postings are provided "AS IS" with no warranties and confer no rights

    Thursday, May 9, 2019 3:48 PM
  • Could you give us the exact errors you're receiving and also tell us what the logs say?

    Another option is to upgrade with SQL Server 2016, once the upgrade is done, then upgrade the SQL Server to 2017.


    Blog: https://thesystemcenterblog.com LinkedIn:


    • Edited by Leon Laude Thursday, May 9, 2019 4:05 PM
    Thursday, May 9, 2019 4:04 PM