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

• Related Articles

• Replication with VMware agent fails with the message: Backup creation failed with code 500

  Challenge  Replication with VMware agent fails with the following error message: "Backup creation failed with code 500, reason: Command '['umount', '/tmp/e9dc80e9-0a54-4991-9003-edeffd7e4920']' returned non-zero exit status 32" Cause In case of using ...

• How to check that a low replication speed is caused by the source machine

  Challenge The Acura Control Panel shows that one of the machines is being replicated with an undesirably low speed. Cause There are several factors that may interfere with a replication and cause a "bottleneck" issue for its speed. But before ...

• 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 ...

• 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 ...

• 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 ...