GUIDE, SCDPM, System Center, Update

Upgrading to DPM 2019 Step-by-Step

In my previous blog post I wrote a guide on how to upgrade to SCOM 2019, this blog post will be a detailed guide on how to upgrade to DPM 2019.

In the guide below, we will be performing a step-by-step in-place upgrade from DPM 1807 to DPM 2019, we will go through every step in detail.

This guide applies to DPM 2016, DPM 1801, DPM 1807


DPM 2019 upgrade paths

The diagram below shows the currently supported upgrade paths for DPM 2019.

Direct in-place upgrade to DPM 2019

  • DPM 2016 -> DPM 2019  
  • DPM 1801 -> DPM 2019  
  • DPM 1807 -> DPM 2019  

Indirect upgrade to DPM 2019

  • DPM 2012 R2 -> DPM 2016 -> DPM 2019  
  • DPM 2012 R2 -> DPM 1801 -> DPM 2019  


For the system requirements for System Center Data Protection Manager 2019, please refer to the Microsoft documentation on the following link:

Pre-upgrade tasks

Before performing the upgrade, there are a few tasks that needs to be done, so we will go though them in detail.

High Level overview of the pre-upgrade tasks

  1. Backup the DPM database.
  2. Stop the DPM services.

Detailed overview of the pre-upgrade tasks

1. Open up the SQL Server Management Studio either on a remote computer or locally on the DPM database server, and then connect to the DPM 1807 SQL instance.

1.1. In the SQL Server Management Studio, expand the Databases, then select the DPM database, right-click it and go to Tasks > and choose Back Up…

1.2. Click on the Add button.

1.3. Now click on the radio button [ … ].

1.4. Provide a name for the DPM database backup, choose a location where to store the backup or go with the default location, click OK once done.

1.5. Make sure that the DPM database is selected and that the backup type is set to Full, click OK to start the backup process.

1.6. Once the backup process has completed, click OK to close window.

2. We will now stop the DPM services, go to Start and search for “Services” and then hit Enter to open the services window.

2.1. Locate the DPM services, as shown below:

2.2. Right-click the DPM service and choose Stop, do the same for the DPM AccessManager service and the DPM Writer service.

2.3. Once all DPM services are stopped we are ready for the upgrade!

Note: If you also have Microsoft Azure backup Server (MABS) installed on the same server, make sure to stop the following services as well:

  • Microsoft Azure Recovery Services Management Agent
  • Microsoft Azure Recovery Services Agent


Upgrade to DPM 2019

We will start by mounting the System Center Data Protection Manager (DPM) 2019 ISO image file and then extract the installation files.

Mount and extract the installation files

1. Mount the Data Protection Manager 2019 ISO image to the DPM server.

2. Run the SC_DPM2019 executable file (Run as administrator) to start the extraction wizard for the DPM 2019 installation files.

3. A System Center Data Protection Manager 2019 extraction wizard will open up, click Next to continue.

4. Check the I accept the agreement and then click Next.

5. Specify the location where the DPM 2019 installation files will be extracted to (For example: C:\System Center Data Protection Manager 2019), and then click Next.

6. Click on Extract to start extracting the DPM 2019 installation files to the location we’ve specified in the previous step.

7. Once the extraction is complete, click Finish.

Perform the DPM 2019 upgrade

1. Head to the location where we chose to extract the DPM 2019 installation files.

2. Right-click the Setup executable file and choose Run as administrator.

3. A System Center Data Protection Manager 2019 installation menu will now appear.

4. Click on Data Protection Manager to start the upgrade to DPM 2019.

5. The Data Protection Manager Setup wizard will now appear, click Next to continue.

6. In the next window the prerequisites check will be done, as this is an upgrade the server name and database should already be filled in automatically, click Check and Install to start checking the prerequisites.

7. Once the prerequisites check is complete, click Next to continue.

Note: The prerequisites check will give a warning saying that the attached DPM database will be upgraded and a backup should be taken before proceeding.

8. Enter the product key for the System Center Data Protection Manager 2019, this is important as the product key can only be entered during the installation/upgrade of DPM, it cannot be entered afterwards! Once the product key has been entered, click Next to continue.

9. The installation location cannot be changed, as this is an upgrade, click Next to continue.

10. If we want to receive updates for our DPM, check the Use Microsoft Update when I check for updates (recommended), if not then choose
I do no want to use Microsoft Update, click Next to start the upgrade process.

11. The upgrade will now take place.

12. Once the upgrade to DPM 2019 has finished, click Close to close the Data Protection Manager Setup wizard.

13. Let’s do a final check to see if our DPM 2019 upgrade was successful, open the Microsoft System Center Data Protection Manager console and click on About in the upper toolbar.

14. We can now see that DPM has been upgraded to version 2019, let’s continue with the post-upgrade tasks.

Post-upgrade tasks

1. Open the Microsoft System Center Data Protection Manager console and head to the Protection pane.

2. We can see that our Protection Group / Protection Groups are in an error state, this is normal after the upgrade.

3. To see more in detail why the Protection Group / Protection Groups are in an error state, expand them.

4. We can see that the Agent is incompatible, this is because we’ve upgraded to a newer version of DPM which means there are new DPM agent versions. To fix this we will need to upgrade the DPM agents, head to the Management pane.

5. Under the Production Servers tab, we can see that the currently installed DPM agent’s status are in “Needs updating”.

6. To resolve this we just have to update the DPM agents, to do this click on the Update Available button for each DPM agent.

Update the DPM agent

1. In the Management pane within the Microsoft System Center Data Protection Manager console, head to the Production Servers tab.

2. We should see a list of all the installed DPM agents in the center, click on Update Available for an agent to start the update process.

3. A warning window will appear, which will notify us that the selected DPM agent will be upgraded, click Yes to continue.

Note: If you upgrade a DPM agent that has protected items (listed under Protected computers with protection agents), the following warning window will appear:

4. The upgrade process might takes a few minutes to complete.

5. Once the DPM agent has been updated, we should see an OK agent status once again, and in the details the new DPM agent version of

6. Perform the upgrade on all the DPM agents in the environment, once all agents are updated we can head towards the last post-upgrade task.

Perform consistency checks

1. In the Microsoft System Center Data Protection Manager console, head to the Protection pane.

2. We can see that the replica is now in an inconsistent state, this is normal after upgrading the DPM version, so we will have to perform consistency checks on our replica(s) to solve this. Right-click on the Protection Group / Protection Groups and select Perform consistency check.

3. A warning window will be shown saying that the consistency check is a time consuming operation, click Yes to start the consistency check.

4. Once the consistency check is running we should see the status of Replica inconsistent, verification in progress.

5. Wait for the consistency check to complete, once it has completed on all the Protection Group / Protection Groups we should see an OK healthy status once again.

We have now successfully upgraded to System Center Data Protection Manager (DPM) 2019 and performed all the necessary tasks!


16 thoughts on “Upgrading to DPM 2019 Step-by-Step”

  1. Thank you for this detailed instruction. My upgrade was successful but the only issue I noticed is that my client sql db name changed for “DPMDB_ComputerName” to “DPMDB_ComputerName+bunch of machine code”. (i.e: DPMDB_xxxxxxxx84ff671d_d9ba_41d0_9f4c_95fee46201bd”. Any idea, and how to get the old name “DPMDB_xxxxxx01” back?

    Thank you


    1. Hello Yao,

      Thank you for using my guide first of all! 🙂

      This is normal/expected behavior that the DPM SQL instance name changes after an upgrade.
      It will certainly not cause any problems and it’s probably not worth the effort to change it, I haven’t tried changing the name myself so I cannot say.

      Best regards,


    1. Hello Joe,

      As of today, Windows Server 2012/R2 is not officially supported, but I believe it will get support later.

      However you ”can” protect a Windows Server 2012/R2 server, but remember that Microsoft might not provide any help/support if you encounter any issues.

      Best regards,


  2. I tried this today, unfortunately i got “Setup cannot grant the account access to the DPM database ID: 832” User is sqladmin a few people said this is due to netbios_name vs FQDN in the sql server name for dpm but netbios is set correctly. The application does work but get some random errors about services not running. Guess im rolling back.


    1. Hi Rick,

      Is the DPM database located remotely or locally?

      During the DPM installation or upgrade you shouldn’t use FQDN as it’s not required.

      If you have performed any DPM upgrades prior to this, you might have several DPM databases that look like DPMDB_DPM_GUID, make sure your account has permissions to all of them.

      Best regards,


  3. Hello Leon, this is Yao again and this is an update. The upgrade was successful on 2 of my production machines but the recovery point creation failed. I am getting error ID 40002 (The VHD containing the replica or one of it’s snapshots could not be mounted or unmounted. (ID 40002) Ensure that the storage containing the VHD is healthy, mounted, and the VHD is not in use by other processes, and retry the operation.) The recommendation action did not solve the issue. I am suspecting some kind of bug in the software. I stop for now the upgrade since we do have many dpm servers in our environment.


  4. I have tried this solution and some other ones that I found on different forum but the problem persists. Fortunately, I only start the upgrade on 2 boxes so I will just wait and see if MS will say anything about it. Thank you again for your help.


  5. I upgraded DPM 2016 to DPM 2019 on Windows Server 2016 and SQL Server 2016. When I try to backup a Windows Server 2019 macheine it failes with error DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 546, WSB Error Code: 0xDD7E0D90). (ID 30229 Details: Internal error code: 0x80990ED0). Any ideas?


    1. Hi Charles,

      It appears that you’re trying to back up a BMR of a Windows Server 2019?

      You might have to increase the default replica size used by DPM for BMR.

      HKLM\Software\Microsoft\Microsoft Data Protection Manager\Configuration

      REG_DWORD: ReplicaSizeInGBForSystemProtectionWithBMR
      (values in hex represent GB)

      If I remember correctly the default one (no registry present/required is set to 30GB), try increasing it to like 100GB.

      Best regards,


  6. Followed this guide, but the upgrade failed. I have the SQL database backup that I made as part of the first step but after re-installing the old version and restoring the database nothing shows up in DPM and I cannot see any instructions anywhere on the Internet on what to do if your DPM upgrade fails 😦


    1. Hi Andrew,

      Could you email me the errors you’re receiving and we can take it from there!


      Best regards,


  7. Hi Leon,

    Great documentation and update guide.

    Really appreciate you putting this time together for us.

    Thank you,



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s