Unable to stop protection

  • Article

Published : April 8, 2005 | Updated : August 17, 2005

Summary

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

Causes

When a volume is removed from a protection group, DPM must delete the synchronization log from the file server and update the file agent so that it stops tracking data changes. In this case, the synchronization log was not deleted and the file agent was not updated because of a disruption in communication between the DPM server and the file server. As a result, the file agent continues to track changes in the synchronization log for the specified volume.

Resolutions

To stop protecting all data sources on the file server

If you no longer want to protect any data sources on the file server, you can locally uninstall the file agent from the file server. For more information, see How to uninstall a file agent.

To retry the stop protection job

  1. On the Alerts tab in the Monitoring task area, group alerts by severity to find the critical “Unable to stop protection” alert.

  2. In the Display pane, select the Unable to stop protection alert.

  3. In the Details pane, click Stop protecting the volume. A new “stop protection” job is scheduled to run immediately.

    Note

    The Stop protecting the volume link disappears from the Details pane after one attempt to retry the job. If the job fails again, you must locally uninstall the file agent from the file server.