Want to replicate a on-prem Hyper V server to Azure Recovery vault, but cannot see the server I want but can see others on the physical HyperV Host

Eric Lee 0 Reputation points
2024-06-15T20:29:35.52+00:00

I am using Azure Recovery Services to replicate a few of my on-prem HyperV servers to my Recovery Vault. I have successfully installed the agent on a few of my on-prem physical HyperV servers already, and are successfully replicating a few servers.

However, on one of my physical Hyper V hosts, I am replicating 2 HyperV servers. I want to replicate a third HyperV server, on the same HyperV hosts, but when I try to select it, it does not display as one of the server I can replicate

Azure Site Recovery
Azure Site Recovery
An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.
670 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Dan Rios 1,735 Reputation points MVP
    2024-06-17T14:30:17.39+00:00

    What's the OS of that particular Virtual Machine? It could be, is it not a supported configuration:

    Windows:

    https://video2.skills-academy.com/en-us/azure/site-recovery/vmware-physical-azure-support-matrix#for-windows

    Linux

    https://video2.skills-academy.com/en-us/azure/site-recovery/vmware-physical-azure-support-matrix#for-linux

    Check connectivity and replication issues: https://video2.skills-academy.com/en-us/azure/site-recovery/vmware-physical-azure-troubleshoot-process-server#check-connectivity-and-replication

    Flowchart showing steps to troubleshoot connectivity and replication.

    And also verify connectivity from the source machine:
    Install the Telnet client on the source machine if you need to. Don't use Ping.

    1. From the source machine, ping the process server on the HTTPS port with Telnet. By default 9443 is the HTTPS port for replication traffic. telnet <process server IP address> <port>
    2. Verify whether the connection is successful.

    I would advise going through all the relevant troubleshooting steps and see if you hit an issue which may solve the issue for that particular VM.