Azure RSV - Replicated Items - Replicate VM to Azure Not Acquire Local VM

Hi parag mewada,

Thanks for Posting your Question in Microsoft Q&A forum

The below documentation describes some common issues and specific errors that we might encounter when we try replicating on-premises VMware VMs and physical servers to Azure using Site Recovery.

• Troubleshoot replication issues for disaster recovery of VMware virtual machines and physical servers to Azure by using Azure Site Recovery - Azure Site Recovery | Microsoft Learn

Please try troubleshooting the issue by verifying the following points

• Two virtual machines with the same instance UUID: If two virtual machines under the vCenter have the same instance UUID, the first virtual machine discovered by the configuration server is displayed in the Azure portal. To resolve this issue, ensure that no two virtual machines have the same instance UUID. This scenario is commonly seen in instances where a backup VM becomes active and is logged into our discovery records. Refer to Azure Site Recovery VMware-to-Azure: How to clean up duplicate or stale entries to resolve.
• Incorrect vCenter user credentials: Ensure that you added the correct vCenter credentials when you set up the configuration server by using the OVF template or unified setup. To verify the credentials that you added during setup, see Modify credentials for automatic discovery.
• vCenter insufficient privileges: If the permissions provided to access vCenter don't have the required permissions, failure to discover virtual machines might occur. Ensure that the permissions described in Prepare an account for automatic discovery are added to the vCenter user account.
• Azure Site Recovery management servers: If the virtual machine is used as a management server under one or more of the following roles - Configuration server /scale-out process server / Master target server, then you won't be able to choose the virtual machine from the portal. Management servers cannot be replicated.
• Already protected/failed over through Azure Site Recovery services: If the virtual machine is already protected or failed over through Site Recovery, the virtual machine isn't available to select for protection in the portal. Ensure that the virtual machine you're looking for in the portal isn't already protected by any other user or under a different subscription.
• vCenter not connected: Check if vCenter is in a connected state. To verify, go to Recovery Services vault > Site Recovery Infrastructure > Configuration Servers > Click on respective configuration server > a blade opens on your right with details of associated servers. Check if vCenter is connected. If it's in a "Not Connected" state, resolve the issue, and then refresh the configuration server on the portal. After this, virtual machine isn't listed on the portal.
• ESXi powered off: If the ESXi host under which the virtual machine resides is in a powered-off state, then the virtual machine isn't listed or isn't selectable on the Azure portal. Power on the ESXi host, and refresh the configuration server on the portal. After this, virtual machine is listed on the portal.
• Pending reboot: If there is a pending reboot on the virtual machine, then you won't be able to select the machine on the Azure portal. Ensure to complete the pending reboot activities and refresh the configuration server. After this, virtual machine is listed on the portal.
• IP not found or Machine does not have an IP address: If the virtual machine doesn't have a valid IP address associated with it, then you are not able to select the machine on the Azure portal. Ensure to assign a valid IP address to the virtual machine, and refresh the configuration server. It could also be caused if the machine does not have a valid IP address associated with one of its NICs. Either assign a valid IP address to all NICs or remove the NIC that's missing the IP. After this, the virtual machine is listed on the portal.

I hope the provided answer is helpful, do let me know if you have any further questions on this Please accept as Yes and upvote if the answer is helpful so that it can help others in the community.

You can check it by using below;

Test-NetConnection <vcenter-ip> -Port 443

Test-NetConnection <vm-ip> -Port 445

also check C:\ProgramData\ASR\home\svsystems\etc\log

If VMs appear locally but not in portal → force a manual refresh in Site Recovery Infrastructure.