In February the first System Center Semi-Annual Channel (SAC) release has been published and now I got the time to install it. So the most recent DPM Version is not 2016 UR4 anymore but 1801.
How to get it? The new release is available from the Volume Licensing Service Center. Simply search for “System Center Data Protection Manager”, then download “System Center DataCenter Core 1801- DataProtection Manager Server & Toolkit MultiLanguage”.
This iso file is about 1.8 GB in size and contains a single msi file, which will extract into a folder of your choice. After extracting all files run setup.exe. The dialog popping up should be well-known (except for the version number):
If you didn’t update your DPM installation to Update Rollup 4 yet, you should do so before updating to 1801. If not you’ll see this error message:
DPM setup detected that this DPM machine does not have latest updates installed. Please install System Center 2016 UR4 Data Protection Manager KB4043316 and then rerun the setup. (ID: 4105)
After that, simply click through the wizard. DPM setup will first ask for your existing database server – in my case this is the local host. Setup will upgrade your DPM2016 database during the installation. Second thing setup want to know is your product key, which is the same one used to install DPM 2016.
In the end you must upgrade your DPM agents as well. It looks like the 2016 UR 3/4 agents are not compatible to 1801 anymore. But usually this should work smoothly. Until now, I had just one single server that needed a restart for completing the agent update.
This is not sufficient as DPM creates a new database. How do you keep using the old one and have DPM update that?
Thank you for the guide.
My upgrade automatically chose the existing database, I just had to specify a username and password.
The upgrade failed though with errorcode 812 regarding the Reporting Services.
Solution was to delete encrypted content, but I had to follow this guide to make it work: https://social.msdn.microsoft.com/Forums/sqlserver/en-US/e9905918-c083-45ed-8b15-ddbff78ff047/cant-delete-encrypted-content-microsoftreportingserviceswmiproviderwmiproviderexception-value?forum=sqlreportingservices
Install went without any issue at all.
Server 2016 – 1801
Database (on box) was found and updated.
Console opened and agents needed to be updated, however I went to 1807 as well
Thanks for this Blog, the DPM upgrade from 2016 UR6 to 2016 1801 and further to 1807 when successful.
I am facing some issue after upgrade.
1. Unable to populate SQL 2016 Always On databases. DPM is not detection it. However with the earlier version 2016 UR6, it was able to populate and backup the databases. Please let if there are any fixes available or any suggestion.
My environment: Win Server 2016, SQL 2016, Locally installed on the server.
2. Tape label text box showing blank, cannot see any label or customize it.
**Please ignore my above message as there were some corrections I did, consider this.
Thanks for this Blog, the DPM upgrade from 2016 UR6 to 2016 1801 and further to 1807 when successful.
I am facing some issue after upgrade.
1. Unable to populate SQL 2017 Always On databases under the protection group. DPM is not detecting it. However, with the earlier version 2016 UR6, it was able to populate and backup the databases. Please let know if there are any fixes available or any suggestion.
My environment: Win Server 2016, SQL 2016, Locally installed on the server.
2. Tape label text box showing blank, cannot see any label or customize it.