• State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 9 replies
  • Subscribers 27 subscribers
  • Views 10837 views
  • Users 0 members are here
Options
Related
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.

Marc L
over 6 years ago

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
  • 0 over 6 years ago
    "server:8006/.../2a41ee58-9f6e-4a88-8551-2ac2f042c598"

    The last part of the string is a GUID which is randomly generated by the agent software (if the protection is agent based). Very little chance that is not unique.

    In the case of agentless protection, it is the UUID of the VM -- thus the id will be the same when you reprotect a machine agentlessly.

    Normally, the issue you face is related to the display name of the agent.
    It may be related with the GUID only if you already have recovery points of that machine on the Core, albeit a conflict almost never happens (the old recovery points are added to the newly protected machine).

    Since the machine with the issue is to become a domain controller, it is worth considering installing the agent to make it as independent as possible (i.e. if the VC goes down). However, this does not solve the problem of agentless protection :)
Reply
  • 0 over 6 years ago
    "server:8006/.../2a41ee58-9f6e-4a88-8551-2ac2f042c598"

    The last part of the string is a GUID which is randomly generated by the agent software (if the protection is agent based). Very little chance that is not unique.

    In the case of agentless protection, it is the UUID of the VM -- thus the id will be the same when you reprotect a machine agentlessly.

    Normally, the issue you face is related to the display name of the agent.
    It may be related with the GUID only if you already have recovery points of that machine on the Core, albeit a conflict almost never happens (the old recovery points are added to the newly protected machine).

    Since the machine with the issue is to become a domain controller, it is worth considering installing the agent to make it as independent as possible (i.e. if the VC goes down). However, this does not solve the problem of agentless protection :)
Children
No Data