Error: The transfer cannot be started: protected volume(s) cannot be obtained from the machine metadata. (4041369)

Rapid Recovery Core displays this message:

Error: The transfer cannot be started: protected volume(s) cannot be obtained from the machine metadata. Please, check the machine device's configuration or change the transfer settings

- or -

Replay.Core.Implementation.Transfer.Validation.Implementation.ProtectedMachineTransferRequestValidationException: The transfer cannot be started: protected volume(s) cannot be obtained from the machine metadata.

Please, check the machine device's configuration or change the transfer settings

This issue is caused by a conflict with Rapid Recovery reading the metadata off of VMware that needs to be corrected within vCenter/vSphere.

Or, machine was restored to dissimilar hardware / went through P2V or V2P processes

The common causes and solutions to this are:

1. If the protected machine is a clone (and thus shares the same UUID as another VM), then Rapid Recovery will have a conflict since there are multiple VMs with the same ID in production. The reason this is a problem is if an ID is shared VC can provide the same virtual machine information for 2 VMs since there are multiple VMs using the same ID, which is not recommended.
2. There are open VMware snapshots that need to be committed/removed from the protected machine. If there are open snapshots either revert them and delete them or go into snapshot manager and delete all (which will commit the snapshots). Afterwards go back into the RR core -> click on the VM under Protected machines -> click Refresh (if it hasn't already).
3. Loss of communication. If there is a random conflict between RR and the VMware environment and either the core, or vCenter need to be restarted at the next possible interval.
4. Machine went through P2V/V2P processes or restored to dissimilar hardware. In this case volume IDs are not the same that were stored on the Core in agent's information. Usually the issue manifests itself by showing 2 C drives: one with 0 bytes size but assigned schedule to it. And another is correct, with no schedule. To resolve that simply remove the schedule from wrong volumes and assign schedule to correct ones. Wrong volumes will disappear.