question

PeterYasuda-0715 avatar image
0 Votes"
PeterYasuda-0715 asked PeterYasuda-0715 answered

ASR Hyper-V to Azure - Enable Replication OK button grayed out, can't select VMs to replicate

I have Azure Site Recovery set up all the way through configuring a replication policy. When I go to Enable Replication > Source Configure, Source, Are you performing a migration? and Source location are all populated correctly, but the OK button is grayed out.

I am trying to replicate a VM from a Hyper-V host on-prem to Azure. The Hyper-V host is registered in the RSV, and I can't find any errors or relevant events anywhere. I've never run into this before. This part has always worked, and I am able to go on to select the VMs.

I am working through troubleshooting in https://docs.microsoft.com/en-us/azure/site-recovery/hyper-v-azure-troubleshoot, but nothing so far.

Has anyone run into this? Thanks

azure-site-recovery
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

PeterYasuda-0715 avatar image
0 Votes"
PeterYasuda-0715 answered

I bypassed the bug in the blade by initiating replication with PowerShell. I used the information in https://docs.microsoft.com/en-us/azure/site-recovery/hyper-v-azure-powershell-resource-manager, but it took me a couple hours to figure out what I needed to do to initiate replication because the article did the thing a lot of the articles do, which is use undefined variables in the example commands.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

SadiqhAhmed-MSFT avatar image
0 Votes"
SadiqhAhmed-MSFT answered

Sorry for the delay in response to your query. I have seen this issue in the past and it turned out to be a bug in the replication blade. If you clear the defaulted process server and then re add it back all the radio buttons become active again and configuration of new servers is possible.

Let me know the status!


Please do not forget to "Accept the answer" wherever the information provided helps you to help others in the community.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

PeterYasuda-0715 avatar image
0 Votes"
PeterYasuda-0715 answered

Hi Sadiqh,

I don't know what you mean by the process server?

The OK button is grayed out at the Source step, so I can't proceed to the Target step: 10485-replicate-source.png


The infrastructure view shows my source location has a single Hyper-V host and and the connection is healthy.

10511-rsv-infrastructure.png



5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

SadiqhAhmed-MSFT avatar image
0 Votes"
SadiqhAhmed-MSFT answered PeterYasuda-0715 commented

Please update all ASR components and then try from new browser.

10459-hyper-v.jpg


For guidance on updating the components see this link.



hyper-v.jpg (128.7 KiB)
· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi Sadiqh,

So you're saying remove the Hyper-V source server, and add it back again. I will try that later, for now I bypassed the bug in the blade by initiating replication with PowerShell. I used the information in https://docs.microsoft.com/en-us/azure/site-recovery/hyper-v-azure-powershell-resource-manager, but it took me a couple hours to figure out what I needed to start replicaition because the article did the thing a lot of the articles do, which is use undefined variables in the example commands.

My VM has replicated and is healthy and protected, so I don't want to reinstall the provider until I fail it over permanently.

Thanks for your answers!

0 Votes 0 ·

Thanks for the update. Glad to know you were able to initiate replication using PowerShell.

0 Votes 0 ·

FYI I did try removing the Hyper-V host and adding it back with a new registration key file. The OK button is still grayed out. I hope that gets fixed soon. I'm going to mark PowerShell as the answer, even though it's really a workaround.

0 Votes 0 ·