Why a failback machine doesn't start

Why a failback machine doesn't start

Challenge

A failback machine doesn't start while the following the message ”Invalid guestid in Configinfo” appears instead.  




Cause

This issue may happen if there are different versions of ESXi installed on the target and on the source.

Usually, this behavior happens if the version, specified in the machine config file, is missing on the target ESXi host.

Solution

Take the following steps to fix the error:

1. Go to the machine on your ESXi, click the "Actions" button, and choose "Upgrade VM Compatibility". 



2. Choose the last version of the ESXi and click the "Upgrade" button.

    • Related Articles

    • Why a replicated/migrated machine doesn't show its network information in VMware ESXi

      Challenge Network information (IP, hostname) of a machine is not shown in VMware ESXi interface after a seemingly successful migration or replication. Cause  No VMware Tools installed on the source machine. Solution In order for the source machine's ...

    • Non-working networking in failover\failback Linux devices.

      Challenge Non-working networking in failover\failback Linux devices. Cause The issue may appear due to the naming of interfaces in Linux. Interface names are based on the NIC type used, so while switching hypervisor (for a Cloud Site or a failback) ...

    • Machine has "Blocked" state in the control panel

      Challenge A machine has "Blocked" status in the Machines Groups section of the ACP. Cause A machine becomes "Blocked", if it's used to start a CloudSite. This is primarily true for VMware target clouds. The "Blocked" state will remain as long as the ...

    • Linux machine can't mount a disk and boot.

      Challenge A Linux machine can't mount a disk and boot. Cause A wrong disk label is written in fstab, so the machine can't mount the disk and boot. Solution 1. Type in your root password and press "Enter" to log in to a maintenance session. 2. Run ...

    • Why Windows replication fails with Hystax VMware Replication Agent - quiesce failure

      Challenge Replication fails when a Windows machine is being replicated with Hystax VMware Replication Agent with the following error message: "Backup creation failed with code 500, reason: An error occurred while quiescing the virtual machine. See ...