Stopping Protection for Co-Located Data

  • Article

Applies To: System Center Data Protection Manager 2010

You can stop protection for co-located data sources like you would for any data source using the Modify Protection Group Wizard and removing the data source from the protection group.

  • If you stop protection with the Retain Data option, DPM will retain the recovery points of the selected data sources as long as the retention range of the data source is not exceeded. After the retention range has been exceeded, DPM will remove the recovery points as part of its daily pruning job. However, the replica of that data source will be preserved until the replica volume is eliminated or the data sources that coexisted with the deleted data source are deleted from protection.

  • If you re-protect the data source that you removed from a protection group in another protection group, the pruning schedule will depend on which of the protection groups has a longer retention range. For more information about the behavior when data sources are migrated out of a co-located protection group, see Moving Between Co-Located and Non-Co-Located Protection Groups

  • If you stop protection without Retain Data, DPM will remove the records of that data source from the DPMDB. The replica volume space that was used by the replica of those data sources will be made available for co-locating more data sources in the same protection group.

  • If you try to restore a database that was once co-located and then later removed, the status of the replica will show as Inconsistent. To handle this situation, run a consistency check on the replica. This will allow you to proceed with the recovery.

See Also

Concepts

Moving Between Co-Located and Non-Co-Located Protection Groups