Forum Discussion
DPM 2019 does not recognize protected SQL Server version after upgrade
Hi, we have upgraded DPM 2019 protected SQL Server from 2016 to 2017 in-place (not SQL hosting DPM database, but SQL we are protecting with). Protection works but DPM still saying that auto-protecti...
I have same problem. Upgraded sql from 2016 to 2019. my dpm looks for version 10 and 14, failing in wmi. but i have wmi populated with 13 and 15. Autoprotection seems to fail. i have DPM 2019 RTM, might try updating it first with some RU.
Just a hint, I reinstalled back to the SQL server these SQL 2016 components:
Client Tools Connectivity
Client Tools SDK
Client Tools Backward Compatibility
And now DPM discovery works. I did uninstall all 2016 stuff from server after the instances were upgraded to 2019 version. Seems DPM agent did not notice this part and keeps using 2016 tools for discoveries.
It is worth someone from MS to probably hotfix this.
Now all is green and I do not really mind those 2016 tools on the server.
PS: I also updated DPM2019 to RU3, but that did not help originally.
Client Tools Connectivity
Client Tools SDK
Client Tools Backward Compatibility
And now DPM discovery works. I did uninstall all 2016 stuff from server after the instances were upgraded to 2019 version. Seems DPM agent did not notice this part and keeps using 2016 tools for discoveries.
It is worth someone from MS to probably hotfix this.
Now all is green and I do not really mind those 2016 tools on the server.
PS: I also updated DPM2019 to RU3, but that did not help originally.