This alert is generated in Data Protection Manager (DPM) when a protected data source is removed from its protection group but DPM is unable to stop protection for the data source.

Causes

When a data source is removed from a protection group, Data Protection Manager (DPM) must delete the volume bitmaps associated with the data source. These volume bitmaps track changes on respective volumes for a data source where protection is being stopped. In this case, the volume bitmaps were not deleted and the protection agent was not updated because of a loss of a network connection between the DPM server and the protected computer. As a result, the protection agent continues to track changes for the specified volume.

Resolutions

The error conditions and recommended actions associated with each “Failed to stop protection” alert are provided in the alert details.

Follow the recommended action in the alert, and retry the job.

To stop protecting all data sources on the protected computer

  • If you no longer want to protect any data sources on the protected computer, you can locally uninstall the protection agent from the protected computer. For more information, see How to Uninstall a Protection Agent.

To retry the job

  1. In DPM Administrator Console, locate the critical “Failed to stop protection” alert. In the Monitoring task area, click the Alerts tab, and then group alerts by severity to help locate the alert.

  2. In the display pane, select the Failed to stop protection alert.

  3. In the Details pane, click Stop protecting the volume. A new, internal “Stop protection” job is scheduled to run immediately. The job is internal; DPM does not display it in the user interface.

    The “Stop protecting the volume” link disappears from the Details pane after one attempt to retry the job. If the job fails again, the volume is still protected and DPM displays a new alert for the failed stop protection.

Resolved when: The stop protection task succeeds.

See Also

[an error occurred while processing this directive]