none
Upgrade to DPM 2016 not using DPM 2012 r2 database RRS feed

  • Question

  • We are attempting to upgrade to MS DPM2016. I have built a new server with Windows Server 2016 and MS SQL 2014. I restored the DPM database from our DPM 2012 r2 server to the new DPM server. I wanted the new DPM 2016 server to use or migrated the data for the new DPM 2016 server. It looks like it did not migrate the old DPM data into the DPM2016 database.                                                                                              
    Wednesday, June 28, 2017 5:05 PM

All replies

  • Same problem here... I followed the instructions of the next page :https://docs.microsoft.com/en-us/system-center/dpm/upgrade-to-dpm-2016 with no success. Any help please?
    Wednesday, July 19, 2017 10:11 PM
  • I don't know that the method you are trying to do is a supported method of upgrade. There are going to be database structure changes in the DPM 2016 DB vs the 2012 R2 DB. The data itself is not stored in the DPM database but only pointers to the DB. DPM 2016 will also want to use ReFS rather than the old volume structure.

    There is an in place upgrade path outlined from this site. from this site https://docs.microsoft.com/en-us/system-center/dpm/upgrade-to-dpm-2016 

    - Upgrade DPM 2012 R2 to DPM 2012 R2 Update Rollup 10. You can obtain the Update Rollups from Windows Update.

    - Upgrade DPM 2012 R2 Update Rollup 10 to DPM 2016.

    - Update the agents on the protected servers.

    • - Upgrade Windows Server 2012 R2 to Windows Server 2016.
    • - Upgrade DPM Remote Administrator on all production servers.
    • - Backups will continue without rebooting your production server.

    If you are attempting to move to new hardware then you would need to treat the new hardware as a restore of DPM and this article outlines the process you would use but would not retain recovery points on disk https://social.technet.microsoft.com/Forums/en-US/81c9af8b-ff30-457f-b250-812c0a60d1a5/migrate-data-from-one-dpm-to-another?forum=dpmsetup and then perform an in place upgrade of DPM.

    Otherwise you could build the new DPM server as 2016 and configure protection to the new DPM server and stop protection on the existing DPM server retaining recovery points until you have the retention you require on the new DPM server. Then retire the old DPM server.

    I've not seen an official swing migration method for DPM as yet.

    Thursday, July 20, 2017 10:30 PM