none
Upgraded to SP1, went from prod to Eval RRS feed

  • Question

  • We've done a great thing. In our production environment running SCDPM 2012 RU3, we've installed SP1 and then RU3 for SP1.

    Unfortunaly, the installation-media for SP1 was most likely from technet, so we ended up with additional SQLinstances; MSDPM2012$Eval.

    All protectiongroups are visible (but of course out of sync cause of the upgrade) and in About DPM it says 180 days left of eval.

    Would it suffice to register the correct serial with powershell, then modify the Conectionstrings in the registry to have our current installation run in "full" mode again?

    We would have just reinstalled SP1 with the correct media but we're unsure on this since we've also installed RU 3 afterwards.


    Ivarson

    Tuesday, September 24, 2013 8:03 AM

Answers

  • Hi,

    I would recommend that you backup the DPM 2012 Sp1+UR3 Database, Un-install the eval version of DPM 2012 Sp1 and SQL Server instance.  Re-install DPM 2012 Sp1 using retail media, install UR3 update, then restore the DPMDB. 


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Tuesday, September 24, 2013 4:02 PM
    Moderator

  • Q1) So switching from production- to eval-mode doesnt "mess" the DPMDB up or so, but only gives the new SQL-instance a name containing eval (in addition to a timebombed sql)?

    A2) Correct, there is nothing unique between Eval DB and Retail DB.  What ever version+update level the EVAL DB is at - you can always install DPM fresh using that same RTM version and install +update - then restore DB that matches.

    Q2)  Do all DPM-upgrades have markers in the DPMDB, so that database-procedures are skipped if the upgrade is being executed twice involving the same db?

    A2)  A DPMDB can only be "upgraded" once per version.  Should an upgrade fail, we should roll-back the DB to pre-upgrade state. 



    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    • Marked as answer by Ivarson Wednesday, September 25, 2013 8:19 PM
    Wednesday, September 25, 2013 8:08 PM
    Moderator

All replies

  • Hi,

    I would recommend that you backup the DPM 2012 Sp1+UR3 Database, Un-install the eval version of DPM 2012 Sp1 and SQL Server instance.  Re-install DPM 2012 Sp1 using retail media, install UR3 update, then restore the DPMDB. 


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Tuesday, September 24, 2013 4:02 PM
    Moderator
  • Thanks Mike.

    After discussions with Mr Hedblom here we ended up reinstalling the whole OS (from 2008r2 to 2012) since that was the plan anyway. Our plan was to upgrade the existing dpm 2012 on w2008r2 to SP1 + RU3, then export the DPMDB and reinstall OS, to keep the new OS/DPM installation as Clean as possible .

    So we _could_ have taken a backup of the DPMDB even though it was upgraded to Sp1+RU3 with evaluationmedia, and install dpm2012sp1+ru1 directly on the new OS?

    We took the safe-pill this time by restoring the first dpmdb-backup since we weren't sure what state the eval-upgraded one was in.

    So switching from production- to eval-mode doesnt "mess" the DPMDB up or so, but only gives the new SQL-instance a name containing eval (in addition to a timebombed sql)?

    An admin should OF COURSE know what media to use when upgrading prod, but i'd really encourage some kind of warning/hints during upgrade in this scenario.

    I did try to reinstall the correct SP1 over the eval-version but it ended up with missing CAB-files.

    Thanks.


    Ivarson


    • Edited by Ivarson Wednesday, September 25, 2013 7:46 PM typo
    Wednesday, September 25, 2013 7:44 PM
  • Do all DPM-upgrades have markers in the DPMDB, so that database-procedures are skipped if the upgrade is being executed twice involving the same db?


    Ivarson

    Wednesday, September 25, 2013 7:50 PM

  • Q1) So switching from production- to eval-mode doesnt "mess" the DPMDB up or so, but only gives the new SQL-instance a name containing eval (in addition to a timebombed sql)?

    A2) Correct, there is nothing unique between Eval DB and Retail DB.  What ever version+update level the EVAL DB is at - you can always install DPM fresh using that same RTM version and install +update - then restore DB that matches.

    Q2)  Do all DPM-upgrades have markers in the DPMDB, so that database-procedures are skipped if the upgrade is being executed twice involving the same db?

    A2)  A DPMDB can only be "upgraded" once per version.  Should an upgrade fail, we should roll-back the DB to pre-upgrade state. 



    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    • Marked as answer by Ivarson Wednesday, September 25, 2013 8:19 PM
    Wednesday, September 25, 2013 8:08 PM
    Moderator