Release Notes for DPM 2007 SP1

Applies To: Data Protection Manager, System Center Data Protection Manager 2007

These release notes provide information about Microsoft System Center Data Protection Manager (DPM) 2007 Service Pack 1 (SP1).

The Release Notes document is available only online, not on the installation media, and is updated periodically.

General Information

You can locate general information about DPM 2007 SP1 in the following resources:

Uninstalling DPM 2007 SP1

You cannot uninstall Data Protection Manager (DPM) 2007 Service Pack 1 (SP1). You must uninstall the DPM 2007 application to uninstall the service pack.


Before you uninstall DPM 2007, perform a full backup of your DPM Server. Verify that a backup of the DPMDB 2007 SP1 database is available before uninstalling DPM.

To uninstall DPM 2007 SP1

  1. In Control Panel, click Add or Remove Programs, and then click Change or Remove Programs.

  2. Under Currently installed programs, select Microsoft System Center Data Protection Manager 2007 SP1, and then click Change/Remove.

    The DPM Setup Wizard starts in uninstallation mode.

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

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

  5. When uninstallation is complete, click Close.

  6. Install DPM 2007 and all of the updates that existed at the time of the DPMDB database backup.

  7. Restore the DPMDB database. For information about restoring a database, see How to Recover DPM Databases (

  8. Run a consistency check for all the backed up data.

Known Issues to Read before Installing

The following list highlights known issues that are important to read before you install DPM 2007 SP1. For more information about other known issues, see Additional Known Issues for DPM 2007 SP1. For more information about solutions when you encounter problems with DPM 2007, see DPM 2007 Known Issues (

  • In the case of a mirrored SQL Server database that is currently being protected by DPM 2007, backups will start failing when DPM 2007 SP1 is installed on the DPM server. This occurs because DPM 2007 treats a mirrored database as a standalone database but DPM 2007 SP1 identifies it as a mirrored database. You will be alerted that the backups are failing. Remove protection (with retain data) for the SQL Server database and re-protect it.

  • Global Options does not appear on the Actions pane after you install DPM 2007 SP1. For more information, see Additional Known Issues for DPM 2007 SP1.

  • To configure disaster recovery for folders or volumes on mount points, you must switch protection from the primary DPM server to the secondary and then back again. For more information, see Additional Known Issues for DPM 2007 SP1.

  • Installation of DPM 2007 SP1 fails if there is insufficient space to back up the DPM database before installation begins.


    You can find the location of the database by checking the database properties from SQL Server Management Studio.

    If you want to install DPM 2007 SP1 without taking a backup of the DPM database, you can use the following command:
    DataProtectionManager2007-KB959605.exe SKIPDBBACKUP=1 /l*v c:\dpmkb959605.log”.

  • DPM 2007 Management Shell help does not have a localized version. Only the English version is available in the product.

  • DPM 2007 SP1 setup leaves Microsoft Visual C++ Redistributable Package installation files in the root directory. You can manually delete the installation files.

  • You cannot recover single database to original location for Microsoft Exchange 2003 if the storage group contains more than one database.
    If you are protecting a storage group that has multiple databases and one of the databases goes down, subsequent express full backups and consistency checks will continue without any problems. However, recovery points created after this event will not have a dismounted database. You cannot recover the database to the original location because the logs are in use by other databases.
    You can use the following steps to recover the database.

    1. Recover the failed database to a network share from the last good recovery point. You should select the check box to bring the database to a clean shutdown state.

    2. Overwrite the failed database with the recovered version.

    3. Mount the recovered database.