Replication of a windows server 2008 R2 is failing with error code: 547000 Most of the error shows a network issue, but we dont find a trace related to network, Any suggestions?

Thadepalli Sai Kumar 1 Reputation point
2024-03-11T10:08:27.84+00:00

Replication of a windows server 2008 R2 is failing with error code: 547000 Most of the error shows a network issue, but we dont find a trace related to network, Any suggestions? Error:

07:26:10:The command C:\Program Files (x86)\Microsoft Azure Site Recovery\agent\AzureRcmCli.exe completed within given timeout period -1

07:26:10:Exit code returned by command: 2

07:26:10:Register machine Iteration: 1 Exit code: 2

07:26:10:Reading value InstallDirectory from key InstallDirectory

07:26:10:Agent install location : C:\Program Files (x86)\Microsoft Azure Site Recovery\agent

07:26:10:Writing to INI file Section 'vxagent.transport', Key 'Hostname', Value ''. File Path 'C:\Program Files (x86)\Microsoft Azure Site Recovery\agent\Application Data\etc\drscout.conf'

07:26:10:Removing key from INI file Section 'vxagent', Key 'ExternalIpAddress'. File Path 'C:\Program Files (x86)\Microsoft Azure Site Recovery\agent\Application Data\etc\drscout.conf'

07:26:10:Setup was unable to connect to Azure service to complete required actions. Configuration failed.

07:26:26:Updating configuration status as Failed in registry.

Azure Site Recovery
Azure Site Recovery
An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.
671 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Pabitra Kumar Sikdar 80 Reputation points Microsoft Employee
    2024-04-29T11:31:54.4533333+00:00

    Hello @Thadepalli Sai Kumar

    Based on the error code you provided, it seems that you are trying to replicate a Windows Server 2008 R2 machine to Azure using Azure Site Recovery and you are encountering error code 547000. This error code usually indicates that there is a network issue preventing replication from occurring. However, you mentioned that you are unable to find any trace related to network. In this case, I would recommend checking the following: 1. Check if the replication target storage account is provisioned correctly and has enough space to accommodate the replicated data. 2. Ensure that the virtual machine is running the latest version of Integration Services. 3. Check if there are any anti-virus software or firewalls that might be blocking Azure Site Recovery. You can learn more about folder exclusions required for Azure Site Recovery in the following link: https://docs.microsoft.com/en-us/azure/site-recovery/vmware-azure-set-up-source#azure-site-recovery-folder-exclusions-from-antivirus-program 4. Verify that the virtual machine is not experiencing high churn rate. If the data change rate (write bytes/sec) on the listed disks of the virtual machine is more than the Azure Site Recovery supported limits for the replication target storage account type, then replication may fail. You can learn more about Azure Site Recovery limits in the following link: https://docs.microsoft.com/en-us/azure/site-recovery/site-recovery-vmware-deployment-planner-analyze-report#azure-site-recovery-limits If none of the above suggestions help, then I would recommend checking the logs for more information on the error. You can find more information on how to troubleshoot replication issues for disaster recovery of VMware VMs and physical servers to Azure using Azure Site Recovery in the following link: https://docs.microsoft.com/en-us/azure/site-recovery/vmware-azure-troubleshoot-replication I hope this helps! Let me know if you have any further questions.

    0 comments