Move/Upgrade DPM 2010 to Server 2012 then Upgrade to DPM 2012 RRS feed

  • Question

  • My current configuration is:

    DPM 2010 on Windows 2008R2 (x64) Server with a local SQL Instance (MS SQL 2008 build 10.00.2573)

    I want to upgrade to DPM 2012, on a different server running Windows 2012 with a remote SQL 2012 Instance.

    Is it possible to combine the following steps: (Moving DPM Server to a different computer)

    Then (Upgrading to System Center 2012-Data Protection Manager)

    First Question:

    How to upgrade the DPM 2010 Database instance from a local SQL 2008 build 10.00.2573 to a remote instance of SQL 2012 (latest build).

    Second Question:

    If there is a problem, is it possible to "roll back" to my DPM on the existing 2008R2 machine if some process of this upgrade and move fails?

    Third Question:

    Would it be better to just "fresh install" all the new systems and software and migrate the Protected data from DPM 2010 (SQL 2008) to DPM 2012(SQL 2012?

    I have licenses for all of the above Server 2012 Data Center, SQL 2012, and System Center 2012 and I plan on having the SQL 2012, DPM 2012, and System Center Configuration Manager 2012 all running on separate HyperV Guests.

    Any additional steps that I need?

    Any caveats to this process and final configurations?

    Any links to additional documents that I am missing or should include?

    Thanks in advance to any assistance or recommendations?


    Wednesday, April 3, 2013 2:39 PM

All replies

  • As far was I know the only way to change the DB (filesystem) location is during a reinstallation of DPM on a new OS. But if you are allowed to move from local to remote SQL you should verify.

    Here is what I would do if the above was indeed supported:

    • Backup DB and move backup to safe location
    • Reinstall DPM server with Windows 2012 but keep disk based recovery points
    • Import dynamic disks (previous disk based backups)
    • Prepare remote SQL server with SQL 2012
    • Restore DB to SQL 2012
    • Install DPM 2012 SP1 and refer it to remote DB
    • Run dpmsync -sync
    • Run CC jobs

    If this fails you can always go back by reinstalling with the previous OS versions and restoring the DB backup.

    Thursday, April 4, 2013 8:54 AM