Franklin Aldridge
This is because the host in the Hyper-V cluster has multiple IP addresses. Prior to version 8.0, the system only records the IP addresses in the database in the default order of Hyper-V's default IP addresses and attempts to connect only to the first IP address. If the backup system's network is not within this IP address range, the backup will fail with a connection error.
Solution:
Log in to the backend database and check the host table's detail to see if there are multiple IP addresses: select * from vm_host\G (The detail field typically contains multiple IP addresses, and the first IP address will be automatically connected by default).
Modify the host's detail field, placing the IP address you want to connect to first and the remaining IP addresses in the following positions.
update vm_host set detail = "Connectable IP 1, Unconnectable IP 2" where host_id = "Host_ID to be modified";
Synchronize in the foreground, refresh the Hyper-V cluster, and then run a task. The backend log will typically display the connected IP address. Verify that the IP address has changed. After resolving the issue, exit the database.
Please feel free to contact us with any questions.
