none
DPM 2010 - Can I move DPM Database from Remote to Local SQL Servers During Upgrade? RRS feed

  • Question

  • Currently we have 2 x DPM 2007 SP1 ready to be upgraded. Both of these currently have the DB's hosted on a remote instance of SQL2005. Now I need to bring the DB's back local to run a local instance however the install process won't allow me to select local.  

    Is there an easy way to migrate the databases back to the local machines?

    • Moved by Praveen D [MSFT] Monday, July 19, 2010 6:16 AM Moving to DPM Setup Forum (From:Data Protection Manager)
    Sunday, July 18, 2010 8:23 AM

Answers

  • Hi mdqray

    In order to move the DPM 2007 Database from a SQL server to the DPM server, you need to do the following

    • Stop DPM service on the DPM  to guarantee that there is no backup running.
    • Backup the DPM Database on SQL server “Full backup bak file”
    • Uninstall DPM Server but make sure to choose to retain data
    • After rebooting the DPM server, Install DPM  and choose install the database on the local machine.
    • Remember to install service pack and any hotfix /patches
    • After the installation is successful, stop DPM service.
    • Restore the DPM database on the SQL server of the DPM server using DpmSync –RestoreDb –DbLoc location –InstanceName server\instance]
    • example

      DpmSync –RestoreDb -DbLoc G:\DPM\Backups\2005\November\DPMDB.bak

    • After you restore the DPM database, to synchronize the databases, you run the following command on the DPM Server
    • DpmSync -Sync
    • DpmSync is a  tool to restores the DPM database, synchronizes the DPM database with the replicas in the storage pool, restores the Report database, and reallocates missing replicas.
    • DpmSync –RestoreDb –DbLoc location –InstanceName server\instance].

    Hopes this will answer your question

    BR

    Robert Hedblom

    http://robertanddpm.blogspot.com

     


    Check out my DPM blog http://robertanddpm.blogspot.com
    Sunday, July 18, 2010 8:43 PM
    Moderator
  • No you cannot move the database from remote to local during upgrade.

    First move the database to local as described in steps above and then perform the upgrade.


    Thanks, Nutesh Garg [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights
    Monday, July 19, 2010 6:12 AM
  • Hello Matt,

    To know the version of the database, use the query: Select * from tbl_dpm_installedupdates. This will list out the KB numbers of installed updates.

    When you restore a primary DPM server to another server, there will be issues owing to permissions. Please see: How to Reestablish Protection After Recovering the Primary DPM Server ... - http://technet.microsoft.com/en-us/library/bb963870.aspx. You might have to use Attach-ProductionServer.ps1 on the DPM server. As long as the disks are attached to the server you run DPMSync on, you will not run into problems. Please check the helath of disks in Storage Manager before you run dpmsync.

    Please reference - Using DPMSync - http://technet.microsoft.com/en-us/library/bb808877.aspx for restore operations.

    If you are worried about the backed up database, simply check the backup by restoring it to another SQL server / instance and see if you are able to browse the tables, etc.


    Regards, Rajeev Narshana [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights
    Saturday, August 7, 2010 9:15 PM
    Moderator

All replies

  • Hi mdqray

    In order to move the DPM 2007 Database from a SQL server to the DPM server, you need to do the following

    • Stop DPM service on the DPM  to guarantee that there is no backup running.
    • Backup the DPM Database on SQL server “Full backup bak file”
    • Uninstall DPM Server but make sure to choose to retain data
    • After rebooting the DPM server, Install DPM  and choose install the database on the local machine.
    • Remember to install service pack and any hotfix /patches
    • After the installation is successful, stop DPM service.
    • Restore the DPM database on the SQL server of the DPM server using DpmSync –RestoreDb –DbLoc location –InstanceName server\instance]
    • example

      DpmSync –RestoreDb -DbLoc G:\DPM\Backups\2005\November\DPMDB.bak

    • After you restore the DPM database, to synchronize the databases, you run the following command on the DPM Server
    • DpmSync -Sync
    • DpmSync is a  tool to restores the DPM database, synchronizes the DPM database with the replicas in the storage pool, restores the Report database, and reallocates missing replicas.
    • DpmSync –RestoreDb –DbLoc location –InstanceName server\instance].

    Hopes this will answer your question

    BR

    Robert Hedblom

    http://robertanddpm.blogspot.com

     


    Check out my DPM blog http://robertanddpm.blogspot.com
    Sunday, July 18, 2010 8:43 PM
    Moderator
  • No you cannot move the database from remote to local during upgrade.

    First move the database to local as described in steps above and then perform the upgrade.


    Thanks, Nutesh Garg [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights
    Monday, July 19, 2010 6:12 AM
  • Thanks Robert for your help.

    I thought this might be the solution if there was not a way of doing it through the setup. My concern is that I will un-install DPM and re-install and then I won't be able to get the DB restorded. Then I won't have a working backup. 

    To fix this I installed a temporary DPM server and tried to restore the DB to see if it would work. The restore worked however the DPM console would not load. Does the server have to be the same name? How can I check that the Database version is the same as the Software version? Are there any options to preserve what we have in case it fails so we can roll back?

    Cheers

    Matt

    • Edited by mdgray Monday, July 19, 2010 12:50 PM spelling
    Monday, July 19, 2010 12:48 PM
  • Hi Mat

    When I have made a disaster recovery of a DPM server I have always used the same name just to be sure. Regarding your question with the version look into the version of your DPM server in your console (of the working one).

    Q1: When you did your restore, did you use the dpmsync cmdlet? Did you point out the old database?

    Q2: Regarding your replicas and recoverypoints of your proteced data, is it stored on a SAN, DAN, NAS that can be cloned?

    I think that DPM will be "a little bit worried" if the volume ID's of the replicas and revocerypoint arent found in the servers disk-setup, that's why it could be a good thing of making a clone of your storage and attatch it to the "new" DPM server.

    BR

    Robert Hedblom


    Check out my DPM blog http://robertanddpm.blogspot.com
    Monday, July 19, 2010 9:45 PM
    Moderator
  • Hello Matt,

    To know the version of the database, use the query: Select * from tbl_dpm_installedupdates. This will list out the KB numbers of installed updates.

    When you restore a primary DPM server to another server, there will be issues owing to permissions. Please see: How to Reestablish Protection After Recovering the Primary DPM Server ... - http://technet.microsoft.com/en-us/library/bb963870.aspx. You might have to use Attach-ProductionServer.ps1 on the DPM server. As long as the disks are attached to the server you run DPMSync on, you will not run into problems. Please check the helath of disks in Storage Manager before you run dpmsync.

    Please reference - Using DPMSync - http://technet.microsoft.com/en-us/library/bb808877.aspx for restore operations.

    If you are worried about the backed up database, simply check the backup by restoring it to another SQL server / instance and see if you are able to browse the tables, etc.


    Regards, Rajeev Narshana [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights
    Saturday, August 7, 2010 9:15 PM
    Moderator
  • Hi, As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as "Answered". Either the previous steps should be helpful for many similar scenarios and will be marked as answer, or this post will be marked as answer in order to close the thread. Feel free to re-open the thread if you have additional information about this specific case or to open a new thread for a new case. In addition, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks,


    Bob Cornelissen - BICTT (My Blog about SCOM) - MVP 2012 and Microsoft Community Contributor 2011 + 2012 Recipient

    Sunday, November 11, 2012 10:05 AM
    Moderator