Problem: During a failover, the recovery VM is not started when the protected VM is in a cluster (MSCS or Always On) with RDM or it has Thick Eager Zero VMDK disks
Error: “Failed to get reflection data for VM” when failing to commit a Failover after VM migration to Azure
Error: “Conversion Task For ImportVM Was Canceled. Internal Error Message: ClientError: Unsupported Windows OS” when Attempting Recovery to AWS
Error: “Failed to power on Failed setting VM vm-xxx to power state On Message: The host does not have sufficient CPU resources to satisfy the reservation”
Problem: Re-IP is Executed Upon Failover When The Recovery VM Wants To Keep The Same Static IP As The Source VMs