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

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

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 have 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 a 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.

  2. Run synchronization for each volume in your protection groups. For more information, see How to Synchronize a Replica.

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

You must perform the following procedures to successfully repair DPM:

  1. Back up the DPM database.

  2. Uninstall DPM.

  3. Delete the DPM database.

  4. Reinstall DPM.

  5. Restore the DPM database.

To back up the DPM database

  1. From an elevated command prompt window, type cd <drive letter>:\Program Files\Microsoft Data Protection Manager\DPM\bin, and then type DPMBackup.exe -db.

  2. In the console tree of the backup program, navigate to \Program Files\Microsoft Data Protection Manager\DPM\Volumes\ShadowCopy\Database Backups. The file name of the DPM database backup is DPMDB.bak.

  3. Select the media to which you want to back up the database.

  4. Start the backup.

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 Microsoft System Center Data Protection Manager 2010 and then click Uninstall/Change.

    The DPM 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 Start menu, 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.

    Note
    The default instance name for a local database installation is MS$DPM2010$.
  3. Expand Databases, right-click the DPMDB database, and then click Delete.

  4. Click Yes to confirm the deletion.

To install DPM

To restore the DPM database using the DpmSync tool

  1. From an elevated command prompt window, type DpmSync –restoredb –dbloc <DPMDB location>, and then press ENTER.

    Note
    The default location of DPMDB is C:\Program Files\Microsoft DPM\DPM\DPMDB. When you use an existing instance of SQL Server for DPM, the default location of DPMDB is the path of the instance of SQL Server where the SQL databases are located.
  2. From the command prompt, type DpmSync -sync.

  3. After the new installation is complete and the database is restored, in DPM Administrator Console, in the Monitoring task area, 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. For more information about how to perform a manual consistency check, see How to Synchronize a Replica in DPM 2010 Help.

See Also