Failover/Failback
Cloud Site creation fails due to a "Resource CREATE failed: invalid availability zone" error
Challenge Cloud Site fails to launch and returns a similar error message: "Error launching cloudsite <ID> for customer <Name> Creation failed: Stack <ID> went to status CREATE_FAILED due to: Resource CREATE failed: ClientError: resources.WIN-H06N: An ...
How to resolve issues with dynamic disks on Windows machines after replicating on VMware
Challenge Windows virtual machines with dynamic disks may experience issues if replicated with an external VMware agent. Although successfully replicated, these VMs may have their RAID-massives in Resyncing or Failed states after having been ...
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 ...
Failover machine running Windows 2008R2 doesn't boot on Google Cloud Platform
Challenge A Windows 2008R2 failover machine doesn't boot on the GCP cloud. Solution Failover machines need certain packages pre-installed on their systems in order to operate on target clouds : Please note that a Windows 2008R2 machine requires ...
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) ...
Why a machine fails to boot on target site with the message "Timed out waiting for device"
Challenge A machine fails to boot with the message "Timed out waiting for device". Cause During a cross-hypervisor replication, storage device names might change (e.g. /dev/sda might become /dev/vda) Solution Use device paths in /etc/fstab for Linux ...
Why certain cloud functions don't work
Challenge Some specific cloud functions won’t work. The following message can be seen in “VM -> Settings -> Properties” of Azure Web Console: Cause The program “Azure Virtual Machine Agent” is not installed on the Azure instance, therefore, some ...
Why a Windows VM starts on the Cloud Site on Azure with an error message
Challenge A Windows VM is starting on the Cloud Site on Azure with an error message. For example "No network". Cause If a Windows machine is not updated, it might experience problems running on Azure. Solution Please make sure that the updates ...
Network interface is changed during a failover and network becomes unavailable for a VM running Linux OS
Challenge Sometimes network interface is changed during a failover and network becomes unavailable. Cause Some Linux machines require additional configuring. Solution To resolve this issue, the source machine can be configured prior to any ...
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 ...
Migration to AWS fails with the error “Multiple different grub/menu.lst files found”
Challenge Migration to AWS fails with the error “Multiple different grub/menu.lst files found” Cause An Ubuntu Cloud image can be configured so that it can boot using BIOS or UEFI alternatively. Such images have two files named boot/grub/grub.conf. ...
Why a Linux machine doesn't boot in the Cloud Site, "dracut" in the console
Challenge Linux machine doesn't boot in the CS, "dracut" in the console. Cause Linux machine doesn't boot in the CS, enters the dracut debug mode instead: Solution RHEL/CentOS uses a dracut system. By default, dracut-initramfs does not include a qemu ...
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 ...