Share via

Deployment failed while configuring Disaster recovery on a VM

Somil Nanda 20 Reputation points
2025-10-23T14:46:56.4733333+00:00

While configuring Disaster Recover on a VM ( windows 2019), the deployment fails once I start replicating after setting all the parameters in Advance Settings.

error message is - Specified resource with name 'yjED0_ivCKOuhdZFl3LlNeylkW4Fd7NeGS-MIDNo5c8' does not exist. (Code: NotFound)

Azure Site Recovery
Azure Site Recovery
An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.
Answer accepted by question author
  1. Siva shunmugam Nadessin 3,025 Reputation points Microsoft External Staff Moderator
    2025-10-27T12:00:12.76+00:00

    Hello Somil Nanda

    The error message you're encountering indicates that the deployment failed due to a "Conflict" during the process. This usually happens when there's a conflict in the configuration or resources between what you're trying to deploy and existing resources or settings in the environment. A conflict can occur due to various reasons like overlapping resources, permissions issues, or incorrect configurations.

    Here are some steps to troubleshoot and resolve this issue:

    1. Check for Resource Conflicts:
      • Ensure that there are no existing disaster recovery configurations or resources in the same region that might be conflicting with the new deployment.
    2. Permissions:
      • Verify that your account has the necessary permissions to deploy and configure Disaster Recovery on the VM. You might need Contributor or Owner permissions.
    3. Review Resource Group Settings:
      • Check if there are any restrictions or configurations at the resource group level that could be causing conflicts.
    4. Target Region Compatibility:
      • Ensure that the target region you selected is compatible with the replication settings and the required resources.
    5. Deployment Logs:
      • Review the deployment details (error details) to pinpoint the exact conflict that occurred. Sometimes, detailed error messages in the operation details can provide more context on the exact issue.
    6. Retry the Deployment:
      • After checking for any conflicts and ensuring all settings are correct, try redeploying the disaster recovery configuration. It might also help to restart the process and ensure all required configurations are aligned.

    Let us know the above helps and if you further queries?

    0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.