On-prem Hyper-V Replication to Azure Errro

Hello Ehsan Habib,

Thanks for posting your question in the Microsoft Q&A forum.

Here’s what you can do:

Check Service Status: Ensure that the following services are running on your Hyper-V host:

• Recovery Services Agent

Site Recovery Provider You can verify this by opening PowerShell and using the command:

Get-Service -Name cbengine

Inspect Hyper-V Services: Make sure the Virtual Machine Management service is running on your Hyper-V host. If you’re using System Center Virtual Machine Manager (VMM), also ensure that the VMM services are up and running.

Check for Stale Registry Entries:

Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Site Recovery on your Hyper-V host and check for any stale entries. Remove any stale entries if they exist.

Unregister Stale Providers: If there are issues related to stale providers, you can unregister them using:

Import-Module Az.RecoveryServices
Connect-AzAccount
Get-AzRecoveryServicesVault
Unregister-AzRecoveryServicesProvider -ProviderId <provider-id>

Reinstall Site Recovery Provider: If you are still facing issues, you may need to reinstall the Azure Site Recovery (ASR) provider. You can download the latest ASR Unified Setup and run it as an administrator.

Verify Hyper-V Integration Services: Make sure the Hyper-V Integration Services are up-to-date in your guest VMs. You can check the status using:

Get-VMIntegrationService -VMName <VMName> -Name VSS

Connection to Azure: Ensure that your Hyper-V host can connect to Azure. You can check the TCP connections for the process cbengine.exe to see if there's network activity.

If you've gone through these steps and are still facing issues, it might be helpful to know:

• What specific error message are you receiving?
• Are there any event logs or additional information related to the failure?
• Have you made sure that the VM in question meets all prerequisites for Azure Site Recovery?

I hope these tips help you resolve the replication issue! If you need further assistance, feel free to ask.

References:

• Troubleshooting Hyper-V to Azure Replication
• Troubleshoot Azure Site Recovery On-Premise Backup Issues
• Backup and data recovery for Azure Stack
• Azure Site Recovery Documentation

Hi Siva,

Thank you for your prompt response, I have check on the host and cbengine server is not installed on the host as shown below.

Also, I have verified that there is no registry key entry on HKEY_LOCAL_MACHINE\SOFTWARE\Site Recovery path. Let me know if you need further details.

Hello Ehsan Habib,

Kindly follow below steps and see if you are able to resolve the issue.

Check Job Details

• Go to Recovery Services Vault > Site Recovery Jobs.
• Locate the failed job and review the detailed error message.
• This often reveals whether the issue is with host registration, network, or credentials.

Verify Hyper-V Host Registration

• Ensure the Hyper-V host is added and visible in the VMM or ASR configuration.
• If you're using VMM, confirm that:
• The VMM server is registered with ASR.
• The Hyper-V host is part of a valid host group.

Check Network Connectivity

• Ensure the Hyper-V host can reach Azure endpoints required by ASR.
• Validate outbound connectivity to:
• *.blob.core.windows.net
• *.hypervrecoverymanager.windowsazure.com
• *.servicebus.windows.net

Restart ASR Services

• On the Hyper-V host, restart the Microsoft Azure Site Recovery Provider service.
• Also restart the VMM service, if applicable.

Retry Protection

• After verifying the above, go back to the VM and retry enabling protection.
• If the issue persists, consider removing and re-adding the VM to the protection group.

Additional Checks

• Ensure latest ASR agent updates are installed on the Hyper-V host.
• Check for resource quota limits in the target Azure region.
• Review the support matrix for Hyper-V to Azure replication to confirm compatibility.

Hello Ehsan Habib,

Could you please let us know whether you got the chance to look into the answer we have provided?

@Siva shunmugam Nadessin

I have reviewed every setting and its seems fine. Problem is I am unable to create VM due to don't have any Size available in the region or due to my subscription issue. I have opened multiple cases with MS support but have not received any response yet.