Repair DPM

 

Updated: May 13, 2016

Applies To: System Center 2012 SP1 - Data Protection Manager, System Center 2012 - Data Protection Manager, System Center 2012 R2 Data Protection Manager

In the unlikely event of corruption of the Microsoft Windows registry, system files, or the System Center 2012 – Data Protection Manager (DPM) binaries, you can repair DPM by reinstalling it. Repairing DPM involves uninstalling DPM while retaining your data protection configuration, and then reinstalling DPM.

This topic provides step-by-step instructions for repairing DPM, including the following information:

  • What you need to do before you reinstall DPM.

  • What you need to do if you do not plan to reinstall DPM immediately.

  • What happens to protection jobs during the repair process.

  • What procedures you need to use to successfully repair DPM.

  • What you need to do after the uninstallation of DPM is complete and before you reinstall DPM.

Important

Before starting a reinstallation of DPM, we strongly recommend that you back up the DPM database, the Report database, and replicas to tape or other removable storage medium. For more information, see Disaster Recovery.

In most cases, you do not need to uninstall the DPM prerequisite software before you reinstall DPM. However, if the SQL Server 2008 SP1 binaries become corrupted, you might have to uninstall and reinstall SQL Server 2008 SP1 also.

You do not have to uninstall the protection agents from the protected computers to reinstall DPM.

Protection jobs cannot run successfully during a repair operation. Any jobs scheduled to run while a repair operation is in progress will be unsuccessful. Any jobs that are in progress when the uninstallation part of a repair operation starts are canceled. Upon completing the repair operation, DPM automatically attempts to perform any canceled replica creation, synchronization, or consistency-check jobs, but it does not attempt to perform canceled recovery point creation jobs.

Important

If you do not plan to reinstall DPM immediately, before uninstalling DPM, you should do the following:

  1. Disable end-user recovery on the DPM server. For more information, see How to Disable End-User Recovery in DPM Help.
  2. Run synchronization for each volume in your protection groups. For more information, see How to Synchronize a Replica in DPM Help.

Following these steps helps to ensure that users for whom you have denied access to files on protected computers cannot access replicas of those files on the DPM server.

To successfully repair DPM, you must perform the following procedures in sequence:

  1. Back up the DPM database.

  2. Uninstall DPM.

  3. Delete the DPM database.

  4. Reinstall DPM.

  5. Restore the DPM database.

  6. Run DPMSync –sync.

To back up the DPM database

  1. On the computer where your DPM database is located, run DPMBackup.exe with the syntax:

    DpmBackup.exe [-db [-instanceName <name>] [-dpmdbName <name>] [-targetLocation <location>]]

    • If the DPM database is on the DPM server

      On the DPM server, open an elevated command prompt and navigate to the \DPM\bin folder in the DPM installation folder. Then run:

      dpmbackup -db -instancename CustomInstance -dpmdbname DPMDB_NAME -targetlocation C:\target_path  
      

      If you’re using a default instance of SQL Server use local for the instance name:

      dpmbackup -db -instancename (Local) -dpmdbname DPMDB_NAME -targetlocation C:\target_path  
      
    • If the DPM database is on a remote computer

      On the computer where the DPM database is installed, open an elevated command prompt, and go to :Program FilesMicrosoft Data Protection ManagerDPMSQLPrep. Then run:

      dpmbackup -db -instancename CustomInstance -dpmdbname DPMDB_NAME -targetlocation C:\target_path  
      

      If you’re using a default instance of SQL Server use local for the instance name:

      dpmbackup -db -instancename (Local) -dpmdbname DPMDB_NAME -targetlocation C:\target_path  
      
  2. On the computer where your DPM database is located, do one of the following:

    • If the DPM database is on the DPM server

      Go to –targetlocation specified in the DpmBackup command above. The file name of the DPM database backup is DPMDB.bak.

    • If the DPM database is on a remote computer

      Go to –targetlocation specified in the DpmBackup command above. The file name of the DPM database backup is DPMDB.bak.

  3. Copy the database backup file to a secure location that you can access when you are ready to restore your DPM database.

To uninstall DPM

  1. In Control Panel, click Programs, and then click Programs and Features.

  2. In the Uninstall or change a program list, right-click System Center 2012 – Data Protection Manager (DPM), and then click Uninstall/Change.

    The Setup Wizard opens.

  3. On the Uninstallation Options page, select the Retain data option, and then click Next.

  4. On the Summary of Options page, click Uninstall.

  5. When uninstallation is complete, click Close.

To delete the DPM database

  1. On the computer where your DPM database is located, click Start, point to All Programs, click Microsoft SQL Server 2008, and then click SQL Server Management Studio.

  2. In the Server name box, type <computer name>\<instance name>, and then click Connect. The default instance name for a local DPM database installation on the DPM server is MSDPM2012.

  3. Expand Databases, right-click the DPMDB database, and then click Delete.

  4. Click Yes to confirm the deletion.

To install DPM

  • For information about how to install DPM, see Install DPM.

To restore the DPM database using the DpmSync tool

  1. On the computer where your DPM database will be restored, open an elevated command prompt window, go to cd <system drive>:\Program Files\Microsoft DPM\DPM\bin, and run DpmSync –restoredb –dbloc <DPMDB file location>.

    DpmSync restores the DPM database and the DPM Report database, and synchronizes the restored DPM database with the previous state of the DPM system. In the command, ** is the location where you stored the DPM database backup file (DPMDB.bak). For more information about using DpmSync, run DpmSync /?.

    The default location of DPMDB is C:Program FilesMicrosoft DPMDPMDPMDB. When you use a remote instance of SQL Server for DPM, the default location of the DPM database is the path where the SQL database files for the instance are located.

  2. From the command prompt, run DpmSync -sync.

  3. After the new installation is complete and the database is restored, in DPM Administrator Console, in the Monitoring workspace, check for protection jobs that failed during the repair operation. Manually restart any failed jobs.

  4. After you restart the failed jobs, you must perform a consistency check for all data sources.