Hyper-V VMs failing to replicatio to Azure Site Recovery

Question

Hi folks,

I have a Hyper-V host that has been replicating it's two VMs to Azure Site Recovery successfully for the last year. However it has started failing with the following error logged in event viewer for both VMs:

Source: Hyper-V-VMMS

Event ID: 32022

Hyper-V could not replicate changes for virtual machine 'AppServer': The connection with the server was terminated abnormally (0x00002EFE).

In Azure the following error is logged:

Error ID

68501

Error Message

The virtual machine couldn't be replicated. Provider error

Replication for virtual machine 'AppServer' is in error. Fix the error(s) and resume replication. Possible causes

Replication errors occurred for virtual machine 'AppServer' in cloud/site '' because of issues with connectivity to Azure storage.

1. If Identity is enabled on the Recovery Services Vault, please make sure the log/target Azure storage account has the necessary permissions to access the storage account

   a) Go to your Storage account -> Access Control (IAM).
   
   b) Add the below role-assignments (for ARM based storage account) to the Recovery services vault.
   
       1) "Contributor" and,
   
       2) "Storage Blob Data Contributor" for Standard storage or "Storage Blob Data Owner" for Premium storage
   

2. Fix any issues in the Event Viewer logs (Applications and Service Logs - MicrosoftAzureRecoveryServices) on the Hyper-V host server and resume the replication.

Unfortunately the recommendations in the Azure error report are too vague for me to apply, but I have made sure that the Site Recovery client is up to date and tried a reinstall with no improvement.

Answer 1

Summarizing from the discussion (above). @Dylan Walkden, Thanks for sharing the info/solution with the community.

Issue: Hyper-V VMs failing to replication to Azure Site Recovery

Error: Event ID: 32022The connection with the server was terminated abnormally (0x00002EFE). Event ID: 68501: The virtual machine couldn't be replicated. Provider error

Solution: The certificate was expired. Steps to renew the certificate: Log into the Azure portal then go to my Recovery Services Vault, then under "Manage" on the left select "Site recovery infrastructure". In this case, replication is from a Hyper-V host, so, select "Hyper-V Hosts" under the "For Hyper-V Sites". In this list of Hyper-V hosts, click on the three dots ("...") on the right for the Hyper-V host with the issues and click on "Renew certificates" in the menu it presents.

Since the Microsoft Q&A community has a policy that the question author cannot accept their own answer. They can only accept answers by others, I' have summarized and posted the solution/answer to benefit the community users to find the answers quickly.

Answer 2

I was able to open a case with the Azure support team and they were able to identify the issue, it was an expired certificate.

The solution is relatively easy, all I had to do was log into the Azure portal then go to my Recovery Services Vault, then under "Manage" on the left I selected "Site recovery infrastructure". I'm replicating from a Hyper-V host, so I selected "Hyper-V Hosts" under the "For Hyper-V Sites". In this list of Hyper-V hosts it gives all I had to do is click on the three dots ("...") on the right for the Hyper-V host with the issues and click on "Renew certificates" in the menu it presents. Roughly five minutes later the VMs kicked off a successful resync.