The DPM database on the DPM server %ServerName; has been restored from a backup. As a result, the alerts that were generated ...

System Center Data Protection Manager 2012

The DPM database on the DPM server %ServerName; has been restored from a backup. As a result, the alerts that were generated before %DBRestoreTime; do not reflect the current state of alerts on the DPM server.

To synchronize the Operations Manager view with the current state on the DPM server: 
1. In the Operations Manager Operator console, resolve all alerts for the %ServerName;, and the computers that it protects: In Alerts view, display all alerts for Microsoft System Center Data Protection Manager (DPM), sort the alerts by Source, and select the alerts for %ServerName;. To remove the selected alerts, right-click, click Set Alert Resolution State, and click Resolved.
2. On the DPM server, re-publish DPM alerts: In DPM Administrator Console, select Options on the Action menu, click the Alert Publishing tab, and click Publish Active Alerts. This publishes all existing alerts that may require a user action to Operations Manager.

The DPM Central Console is built on top of Operations Manager. It requires few components to be installed both on the Operations ... The DPM CPWrapper Service is not configured correctly for the %MachineName; computer. Exception Message = %ExceptionMessage;. ... The DPM CPWrapper Service is using a certificate for the %MachineName; computer that is not valid. Exception Message = %ExceptionMessage;. ... The DPM database on the DPM server %ServerName; has been restored from a backup. As a result, the alerts that were generated ... The DPM database on the DPM server %ServerName; has been restored from a backup. As a result, the alerts that were generated ... The DPM database on the DPM server %ServerName; has been restored from a backup. As a result, the alerts that were generated ... The DPM database size cannot be reduced. To resolve this alert, you need to increase the free space in the DPM Database volume, ... The DPM job failed for %DatasourceType; %DatasourceName; on %ServerName; because the protection agent did not have sysadmin ... The DPM job failed for %DatasourceType; %DatasourceName; on %ServerName; because the SQL Server instance refused a connection ...