Regresar
-
Título
Unable to link agents to the Hyper-V cluster for licensing purposes -
Descripción
Hyper-V cluster was protected, however it's not possible to link agent-based protected VMs to it. Licensing is still counting separate agents instead of hypervisor CPU sockets -
Causa
Hyper-V cluster added as an agent-based protected machine/cluster instead of following agentless-based protection mechanism -
Resolución
For the RapidRecovery Core to calculate number of CPU sockets, Hyper-V cluster must be added using agentless protection method. Thus, to resolve the issue please do the following:
- remove Hyper-V cluster and its nodes from protection
- click Protect button drop-down, Protect Multiple
- select Hyper-V host or cluster (depends on environment) and follow the wizard. Please make sure that "agentless" checkbox stays checked
- protect at least 1 VM agentlessly. This machine can be removed from protection later
- once VM is protected Hyper-V hypervisor will show in the console
- now it's possible to click on VM agent name, Settings on the right pane, click on Hypervisor and select at least one node to link.
Note: due to the existing defect, it's not possible to link to the Hyper-V cluster name itself, so please select any node for that. Same defect is affecting ability to bulk-link agents by clicking on Hyper-V cluster name in Core console and clicking on Link Agents hyperlink.