This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Cannot protect machine because RR says it's already protected.

We are protecting our VM's agentlessly and only have 1 VM that's causing issues. Whenever I try to add it to protection, RR says it's already protected. This VM has never been protected before so I don't know what's causing RR to think that. We deploy all of our machines via templates so I know it's not a duplicate SID issue or else we would have seen it before. Is there somewhere I can check to get more info on why RR is saying this? Or even better, remedy the situation?

Parents
  • Well I fixed the issue although inadvertently... While trying to remove a VM from being protected, I removed the VCSA by mistake. (Might be a slight UI issue there...). But after everything was gone, it all re-added properly and I had no conflicting issues. Just hoping we don't need to restore anything older than yesterday!
Reply
  • Well I fixed the issue although inadvertently... While trying to remove a VM from being protected, I removed the VCSA by mistake. (Might be a slight UI issue there...). But after everything was gone, it all re-added properly and I had no conflicting issues. Just hoping we don't need to restore anything older than yesterday!
Children
No Data