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: