Forum Discussion

James_Walton's avatar
10 years ago

Cannot delete Recovery Point Set

SSR 2013

When I try to delete a Recovery Point Set I get the message "Successfully deleted 0 policies."

If I edit the policy then use the menu in the top-left corner to try and delete it I get the message "The item is being referenced by one of more other items. You must first delete these items...."

It then provides a link to view the referenced item, which is apparently a filter.

If I look at this filter, I can see it has no members and is not referenced by any other objects.

If I try to delete this filter, it won't let me, with the same error message as above.

Completely stuck now with no idea what to do!

  • This was fixed by installing the latest hotfix for SSR management solution

  • Bit confused .... are you trying to delete the policy or some recovery points? It sounds like you are trying to delete the policy but you said: 'When I try to delete a Recovery Point Set I get the message ...'

  • I think you mean that you are trying to delete the backup policy. Right?

    Can you provide a screenshot that shows this? This will make it clearer ..

  • OK, thanks. So it's deleting a policy then ..

    So is this problem specific to a certain policy? Or have you seen the same issue when trying to delete other policies?

    Also, have you removed the association with the client machines before attempting to delete it? Best way to do this is to disable the policy first, then wait for the client machines to update themselves with the management solution server (by default, the update interval is 1 hour).

  • I can delete other policies without any problem.

    I've tried to remove the server's association by disabling the policy, and also by removing the computer from the Apply/Unapply screen, but it still shows as assigned to 1 Computer in the list.

  • The screenshot shows you are running the 2013 version of the Management Solution. You may want to consider updating to 2013 R2 to see if this helps.

    Other than than, I would recommend opening a support case for this issue - it requires more detailed investigation.

  • This was fixed by installing the latest hotfix for SSR management solution