How do I continue my site recovery migration when I can't select my source target (hyper-v site) but I can see it connected on Azure

Hi Godwin Olarele, Thanks for posting your question in Microsoft Q&A portal

Here are a few follow-up questions that could assist in troubleshooting further

1. Are there any error messages displayed when you try to select the source target?
2. Can you confirm that the Azure Site Recovery provider is registered with your Hyper-V site?
3. Have you checked the permissions on your recovery services vault?
4. Is your Hyper-V site visible in the Azure portal under Recovery Services Vault?

Hi Godwin Olarele, following up to see if you have a chance to check my previous response and help us with requested information to check and assist you further on this. 

Hi Godwin Olarele, Thanks for follow up & sharing the details

The issue is commonly related to the registration and discovery of the Hyper-V hosts within the site.

Here are key points and solutions to consider based on Azure Site Recovery documentation and troubleshooting guides

• After creating the Hyper-V site and adding Hyper-V hosts in the Azure portal under Prepare infrastructure, it is critical that the Azure Site Recovery Provider and Microsoft Azure Recovery Services (MARS) agent are correctly installed on each Hyper-V host and that each host is properly registered with the Recovery Services vault via the vault key.
• Hosts not reporting correctly to Azure due to registration issues can require re-registering the host using the vault key via the DRConfigurator.exe tool on the Hyper-V host. Use the following command on the host to (re)register it:
• Register the server by running this command:

cd "C:\Program Files\Microsoft Azure Site Recovery Provider"
"C:\Program Files\Microsoft Azure Site Recovery Provider\DRConfigurator.exe" /r /Friendlyname "FriendlyName of the Server" /Credentials "path to where the credential file is saved"

• Ensure you have the latest versions of the Azure Site Recovery Provider and MARS agent installed. Compatibility or version mismatch can cause connectivity or visibility issues. Check that you have the latest version. Keep Integration Services up-to-date.
• Check for potential interference if Azure Backup is also configured on the same Hyper-V host, as running Backup and Site Recovery replication simultaneously on the same host is not supported.
• Confirm the Hyper-V host’s status in the Azure portal under Site Recovery Infrastructure > Hyper-V Sites > Hyper-V Hosts to ensure the host is connected and online.
• Make sure the Hyper-V hosts or VMs are not already protected, registered, or associated with a different subscription or recovery vault, which can prevent their visibility.
• Verify that your subscription is registered to use the Azure providers for Recovery Services and Site Recovery, using these commands:

    Get-AzResourceProvider -ProviderNamespace  Microsoft.RecoveryServices
  

• Confirm network connectivity for the Hyper-V host to the required Azure endpoints and that firewalls or proxies are not blocking communication.

If after these checks the servers still do not appear, consider fully uninstalling and reinstalling the Azure Site Recovery Provider and MARS agent on the Hyper-V host. You may also need to clean up old registration keys and certificates by deleting registry keys and associated certificates, then rebooting the host before attempting to register again.

Referral documents:

• https://learn.microsoft.com/en-us/azure/site-recovery/hyper-v-azure-powershell-resource-manager
• https://learn.microsoft.com/en-us/azure/site-recovery/hyper-v-azure-troubleshoot

Let us know if this resolves your issue or if further assistance is required!

Hello Godwin Olarele,

checking to see if you have a chance to check my previous response and helped, do let me know if you have any further questions on this.