Starting with Rapid Recovery 6.2, you are now required to associate a Virtual Agent with a hypervisor in order to use CPU socket licensing with virtual machines protected with the agent software. This change allows a virtual machine to be protected with an agent and continue all backup functions using the agent technology, without charging 1 agent license per virtual machine. Instead, the virtual machine will become a child object of the hypervisor and take on the the hypervisor's per socket licensing.
A single Rapid Recovery license can be used to license 1 physical agent, 1 virtual agent, or 1 CPU socket. The licenses are functionally interchangeable in the Rapid Recovery License Portal. Unless a virtual agent is linked to a hypervisor it will charge 1 agent license and consume 1 license from your license pool.
*** Please note that following the steps in this article to link virtual agents to a hypervisor does not change the backup mechanism. The backups will still be taken using the agent software. This does NOT convert them to agentless backup technology. It only changes how licensing is charged.
To enable linking you must have the hypervisor that hosts the virtual agents added to the core console using agentless backup technology. To do this, you must protect at least one VM on that hypervisor with agentless protection. You do not have to keep that agent protected after you have linked your virtual agents, you simply have to use the agentless protection mechanism to authorize the core to connect to the hypervisor so that it can track CPU sockets on the hypervisor and validate that the virtual agents actually exist on that hypervisor host.
To protect a virtual machine using agentless protection please follow the steps in our user guide to use Rapid Snap for Virtual (agentless) protection.
Once a single virtual machine is protected using agentless backup technology you can then link virtual machines to the hypervisor. There are two ways to link existing virtual agents to a hypervisor. Steps are the same for Hyper-V and VMware hypervisors.