Vmotion causes Rapid recovery to stop protecting a virtual server.

Question

When protecting multiple machines in a VMware environment should we choose the vcenter machine or the individual hosts. We went with hosts, but now when we vmotion a server between hosts, rapid recovery stops protecting it as It can't see it. 
 So this is really 2 questions 
 1.Should we choose the vcenter server when protecting multiple servers using agentless backup. Will this cope with vmotion? 
 2.If the answer to 1 is yes. how do we change to vcenter and not lose all our existing recovery points. 
 I hope this covers it? 
 many thanks 
 
 Richard

Tudor.Popescu · Accepted Answer

Hi Richard: The best bet is to use the VCenter for protecting VMs agentlessly. The reason is that if you protect at ESXi host level, Rapid Recovery is able to find the VM by connected to that specific host. When you VMotion, the VM becomes the "ward" of another host and as such inaccessible through the host you used to protect the VM. Even in the case of protecting via the vCenter, if you do storage vMotion, although the machine will stay protected you may have some surprises if CBT malfunctions due to some VMWare issues.To work around them you may need to update/upgrade your VMWare environment Please check: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2048201 
 Keeping your Recovery points is a more difficult task as RapidRecovery protected machines are identified through a UUID while VMWare ids are based on the name of the VM or the BIOS UUID. The Rapid Recovery agent UUID is stored both in the Registry of the core and in the .vmx file of the protected VM. To find it, open the VM .vmx file and navigate to the following key-value pair: ddprr-apprecovery-agent-id = "<GUID>". After protecting the VM using the VCenter, make sure that the key-value pair is preserved and if it is not, use the original UUID.