Data Protection Manager (DPM) raises this alert for application servers such as Microsoft Exchange Server for any recovery failure, and for file servers and workstations when the recovery completely fails.


Review the alert details in Data Protection Manager (DPM) Administrator Console and take the appropriate action.

Possible causes for the alert include the following:

  • DPM was unable to copy data to the specified recovery destination.

  • The default recovery destination no longer exists or cannot be accessed.

  • You try to recover from a secondary DPM server to the original protected computer when the protected computer is in active protection by a primary DPM server.

For Exchange Server and SQL Server, possible causes include the following:

  • The database mount failed.

  • The database was deleted.

  • The Exchange or SQL Server service is not running.

  • For SQL Server 2005, the SQL writer service has been turned off.

  • There are disk issues on the application server.

  • There are Volume Shadow Copy Service writer issues.

For Exchange Server, possible causes include the following:

  • The Eseutil.exe utility failed to apply the logs on the Exchange Server database files to bring the database to a clean shutdown state.

  • The Exchange database is not allowed to be overwritten by a recovery job.

  • The name of the storage group or database is different from what it was during backup.

  • Exchange writer might be in a bad state. You need to restart the Exchange Information store service.

  • Storage group is deleted.

For Windows SharePoint Services, all the SQL causes are possible, as well as the following:

  • The Windows SharePoint Services writer or the Search writer might not be running or might be in a bad state; you need to restart the writer.

Site and document backup can fail because of the following:

  • The corresponding content database could not be attached to the specified SQL instance.

  • The corresponding content database could not be made a part of the specified recovery farm.

  • A Web application by the name DPMRecoveryWebApplication has not been created on the recovery farm.

  • The export or import operation for the recovery item has failed.

Check to see whether the WSSCmdLets.exe DCOM component on both the recovery farm and the protected farm has been given farm administrator privileges. (This is one of the prerequisites for protecting a farm.)


The error conditions and recommended actions associated with each “Recovery failure” alert are provided in the alert details.

  • On the Alerts tab, rerun the recovery jobs from the link provided.

To get more information, review the alert details on the DPM server that is protecting the data. For information about viewing alert details in DPM Administrator Console, see How to Display Alert Details. For information about viewing job details in DPM Administrator Console, see How to Display Job Details.

  • Start a new recovery job for the data that DPM failed to recover.

    You can run the job again by clicking the recommended action on the alert.
  • Before you recover from a secondary DPM server, make sure that no jobs are running for the protected computer. (This is necessary only for data recovery.)

This alert automatically becomes inactive in DPM seven days after the recovery collection job has failed.

Resolved when: Job completes successfully.

For information about monitoring and managing recovery operations in DPM, see the appropriate chapter for the type of data you are recovering in the DPM 2007 Operations Guide (

See Also