Additional Known Issues for DPM 2007 SP1

  • Article

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

This topic lists the known issues and possible resolutions for System Center Data Protection Manager (DPM) 2007 SP1 TAP Release:

  • DPM agent stops working

  • SharePoint index backups fail during profile import

  • Silent installation does not show restart message

  • DPM Administrator Console stops working when updating protection agents

  • DPM Management Shell stops working

  • Replica or Shadow Copy Volume Resizing in Windows Server 2008

  • Unable to uninstall DPM 2007

  • Global Options not available

  • Enabling disaster recovery for folders and volumes on mount points

  • Cannot recover single database to original location for Microsoft Exchange 2003

  • Microsoft Exchange Generating Large Amount of Log Files

  • Old recovery points not available after migrating data source

  • Unable to browse last database of all recovery points after upgrade

DPM agent stops working

When the recovery of a data source fails, the agent on the protected computer (to which the recovery was taking place) stops working. This causes all current jobs on the protected computer to fail.
The probable reasons for this could be lack of space for the recovered object or DPM may be trying to recover a locked file. Investigate possible reasons for the failure of the recovery to resolve this issue.

Silent installation does not show restart message

The DPM agent installation requires the protected computer to be restarted to complete the installation. If you perform a silent installation, it will not show the message requiring the restart, but the restart is still required to complete the installation.

DPM Administrator Console stops working when updating protection agents

If you are updating many protection agents, DPM Administrator Console may stop working. We recommend that you upgrade no more than 10 agents at a time.

DPM Management Shell stops working

If the version of DPM Management Shell does not match the version of DPM that you are running, it stops working and displays error 4319 – DPM install is successful but reboot is needed.
To avoid this problem, install the version of DPM Management Shell that matches the version of DPM on your server.

Replica or shadow copy volume resizing in Windows Server 2008

If you resize a replica or shadow copy volume in Windows Server 2008, it could lead to VSS not working correctly or even loss of shadow copies. This scenario is untested and we recommend that you do not resize these volumes in Windows Server 2008, to avoid potential problems.

Unable to uninstall DPM 2007

If you get an “Uninstall failed” message when you try to uninstall DPM 2007, try the following steps to see whether the error will resolve.

  1. Open the DpmSetup.log file.

    • For computers that are running on , it is at “%System Drive%\Documents and Settings\All Users\DPMLogs\

    • For computers that are running on Windows Server 2008, it is at “%System Drive%\DPMLogs\

  2. Search the log file for the string "InstallSqlData. Return value 3", starting at the bottom of the file.

  3. When you find the string, open a command prompt window and run the following command
    For 32-bit computers:"msiexec /x {744BCB16-4B0D-4A8C-93F7-2D0276AE6B72} BOOTSTRAPPED=1 SKIPINSTALLSQLDATA.97DDF5B3_3770_4C3E_8673_52BD081E1EFD=1 /l*v c:/install.log"
    For 64-bit computers:"msiexec /x {67750D8C-C240-4B66-B2B1-EE0BAA7FD904} BOOTSTRAPPED=1 SKIPINSTALLSQLDATA.97DDF5B3_3770_4C3E_8673_52BD081E1EFD=1 /l*v c:/install.log"

  4. In Control Panel, open add or Remove Programs and check if DPM 2007 is listed. If it is not listed, then DPM 2007 is successfully uninstalled.

  5. Restart the computer.

Global Options not available

Global Options… does not appear on the Actions pane after you install DPM 2007 SP1.

If you are seeing this issue, click the Monitoring tab and select Subscribe to notifications from the Actions pane or click the Recovery tab and select Configure end user recovery from the Actions pane. Both these actions let you access the Global Options dialog box. Now Global Options appears on the Actions pane.

Enabling disaster recovery for folders and volumes on mount points

Use the following steps to enable disaster recovery for folders or volumes on mount points:

  1. Switch protection for the protected computer from the primary DPM server to the secondary DPM server. For more information, see Switching Protection If the Primary DPM Server Fails

  2. Protect the mount point on the secondary DPM server.

  3. Switch protection back to the primary DPM server.

The folders and volumes on the mount point are available for protection by the secondary server.

Cannot recover single database to original location for Microsoft Exchange 2003 if 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 original location since 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 not select the checkbox to bring the database to a clean shutdown state.

  2. Copy the new log files generated after this backup from the Exchange server to same folder.

  3. Run eseutil to bring the recovered database to a clean shutdown state.

  4. Overwrite the failed database with the recovered version.

  5. Mount the recovered database.

Microsoft Exchange generating large amount of log files

Some mailbox functions result in Exchange generating a large number of log files. Not all of these files need to be backed up. Currently, DPM backups all the logs, resulting in large replicas. You can avoid this situation by cleaning up the log files on the Exchange server before you can take a successful backup. You can do this by making an out-of-band full backup of the affected storage group using NTBackup. For Windows Server 2008, you can use the BETest Tool that is part of the Windows SDK.

Recovery points on volumes without mount points not available after restart

When you restart your computer after migrating a data source, the old recovery points for that data source are not shown in the list of available recovery points on the Recovery tab. This is because the old pair of volumes do not have any mount points.

When a data source is migrated and all the old recovery points expire, DPM deallocates the old pair of volumes. This leaves the new pair of volumes without a mount point. So, the new recovery points present in those volumes are not shown after a reboot.

To be able to see the recovery points, mount the volumes that do not have a mount point and restart the DPM service.

Unable to browse last database of all recovery points after upgrade

After you upgrade DPM 2007 to SP1, you will not be able to browse the last database of a recovery point. This affects only item-level recovery. Recovery of SharePoint farms and Content DBs can still be done.