No hosts with hardware version 'x' and datastore(s) 'xxxx' which are powered on and not in maintenance mode are available.
The vSphere Replication Management Server could not fetch source host (id: '##.##.##.##', name: '#################') health checks endpoint API version. Details:org.springframework.web.reactive.function.client.WebClientResponseException$NotFound: 404 Not Found from GET https://##.##.##.##/hbragent/api/about'.
VMware Live Recovery 9.x
This issue is caused by a DNS resolution failure between the ESXi hosts and the vSphere Replication (VR) appliance.
During recovery orchestration, the system must install or verify the hbr-agent VIB on the target ESXi hosts. If the ESXi hosts cannot resolve the Fully Qualified Domain Name (FQDN) of the VR appliance, the VIB installation fails. Because the agent is missing or inactive, the hosts are reported as incompatible or unavailable for the failover task.
Upon checking esxi logs for the vib installation, we see errors as below.
We see /var/log/esxupdate.log reporting the below reporting 'Name or service not known'
2026-05-18T08:31:53Z Er(11) esxupdate[84364567]: File "/lib64/python3.11/site-packages/vmware/esximage/Transaction.py", line 981, in _getVibsFromUrls2026-05-18T08:31:53Z Er(11) esxupdate[84364567]: raise Errors.VibDownloadError(url, None, str(e))2026-05-18T08:31:53Z Er(11) esxupdate[84364567]: esximage.Errors. VibDownloadError: ('https://#####:443/vib/vmware-hbr-agent. vib', None, "('https://####:443/vib/vmware-hbr-agent.vib', '', '<urlopen error [Errno -2] Name or service not known>')")2026-05-18T08:31:53Z Db(15) esxupdate[84364567]: <<<
To resolve this issue, ensure consistent name resolution across the replication infrastructure:
nslookup <VR-Appliance-FQDN>
nslookup <VR-Appliance-IP>