Azure Site Recovery
An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.
728 questions
Unable to enable replication for VMware On-Premises VMs to Azure
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(131.20000000000002, 43%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAS%3C/text%3E%3C/svg%3E)
Allen Stalker
0
Reputation points
We are attempting to enable Azure Site Recovery for on-premises VMware VMs to Azure.
When attempting to enable replication we are receiving the following errors:
Error ID: 327191
Error Message:
Site recovery configuration failed.
Connection cannot be established to Azure Site Recovery service endpoints.
Error ID:
539
Error Message:
The requested action couldn't be performed by the Replication Provider.
The Provider action failed. Check other errors for more information.
Error ID:
327173
Error Message:
Installation of mobility service on source machine has failed.
Installation of mobility service has failed.
We have validated that the on-premises VMware VMs can reach Azure Site Recovery outbound. We have also tried to validate TLS configurations; all seems to be good there. Any suggestions on how we can proceed?
{count} votes
-
SadiqhAhmed-MSFT 46,866 Reputation points Microsoft Employee2024-11-19T13:57:58.35+00:00 @Allen Stalker Greetings!
The errors you're encountering while setting up Azure Site Recovery (ASR) for replicating on-premises VMware VMs to Azure can stem from several issues, including network connectivity, configuration problems, or issues with the installation of the Mobility Service on the source machines. Let's break down the error messages and the possible solutions:
- Since you’ve mentioned that the VMs can reach Azure Site Recovery endpoints, double-check for any possible outbound traffic restrictions, including proxies, firewalls, or security groups. Ensure that the required ports and URLs for Site Recovery are open.
- Required URLs for ASR:
-
*.blob.core.windows.net -
*.asr.azure.net - Required ports:
- 443 (HTTPS) for all communication to Azure Site Recovery endpoints.
- TLS Configuration: Verify that your network allows the required TLS versions (typically TLS 1.2) for secure communication with Azure endpoints.
- DNS Resolution: Ensure that the VMs have proper DNS resolution to resolve Azure Site Recovery endpoints. Sometimes DNS issues may not be obvious but could still block traffic.
Double-check your Azure Site Recovery vault and Replication settings in the Azure portal. Verify that you’ve selected the correct VMware to Azure replication option and that your on-premises VMware environment is properly configured in the Azure portal. Check that the Azure Site Recovery Provider is installed and running correctly on your on-premises VMware host.
Review the logs for the Mobility Service installation on the source VM. These logs are typically stored under
C:\ProgramData\Microsoft\ASR\home\and will provide more details on why the installation failed. Common reasons for failure include:- Insufficient privileges or permissions to install software.
- Antivirus or security software blocking the installation of the Mobility Service.
- Missing prerequisites on the source VM (e.g., .NET Framework versions or other dependencies).
If automatic installation fails, you can attempt to install the Mobility Service manually:
- Navigate to the Azure Site Recovery Vault in the Azure portal.
- In the Replication section, locate your source VMware VM and choose Install Mobility Service manually.
- Download the Mobility Service installer from the ASR vault and manually install it on the VM.
- If the manual installation fails, check the logs for any errors or permissions-related issues
Review Replication Provider Logs: The Replication Provider is responsible for managing replication tasks. These logs can offer more insights into what went wrong.
- Logs are typically located in
C:\ProgramData\Microsoft\AzureSiteRecovery\on the on-premises server running the ASR provider. Check for any errors in these logs and investigate further based on the details you find.- Look for errors related to authentication, communication with the Azure Site Recovery service, or permissions issues.
Check Permissions and Role Assignments: Verify that the service principal or account used by Azure Site Recovery has appropriate permissions (e.g., Contributor or higher) to perform operations on the Recovery Services Vault, the source VMware infrastructure, and the target Azure subscription.
Once you've addressed the network, permissions, or installation issues, try to re-enable replication for your VMware VMs in Azure Site Recovery. Sometimes a simple restart of the replication process or the on-premises ASR components may help clear out transient errors.
Hope this helps. If problem persist, then the best option would be to contact Azure technical support team by raising a support ticket. The ticket enables you to work closely with the support engineers and get a quick resolution to your issue.
Here is the link - https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request to create support case.
- Since you’ve mentioned that the VMs can reach Azure Site Recovery endpoints, double-check for any possible outbound traffic restrictions, including proxies, firewalls, or security groups. Ensure that the required ports and URLs for Site Recovery are open.
Sign in to comment
Sign in to answer