Druva runs a few checks before migrating an instantly restored virtual machine to production. These checks look for issues that can cause your Migrate to Production job to fail before the migration job has even started. The Migrate to Production job uses VMware APIs to perform the migration. The identified issues are all VMware issues that you must fix before migrating the instantly restored virtual machine to production.
The following table lists a few of the VMware issues that can cause the pre-checks to fail. We encourage you to look up the VMware Knowledge Base for issues beyond the ones listed below.
Migrate to Production Pre-checks
|The target host does not support the virtual machine's current hardware requirements.||See the VMware article to determine the cause of the error and its resolution.|
|Currently connected network interface '<Network adapter 1>' uses network '<DVSwitch>: <UUID>, which is not accessible.||See the VMware article to determine the cause of the error and its resolution.|
|The vMotion interface is not configured (or is misconfigured) on the Source host <Host>.||See the VMware article to determine the cause of the error and its resolution.|
|The virtual machine uses network <'VM Network’>. Since the operation is being conducted across datacenters, this network may not be the same network on the source and destination. This is because network names are only unique within a datacenter.||
You may get this warning while migrating across data centers. Though you can still run the Migrate to Production job, we recommend fixing the issue before migrating the VM to your production environment.
To resolve this issue, ensure that you have configured a network with the same name on the destination ESXi host.
|Too large clock skew was detected.||The system time on the virtual machine must be in sync with the time on the host. A time drift between the guest virtual machine and the host can cause issues while migrating the virtual machine to production, restoring to a recovery point, shrinking the virtual disk, or restarting the VMware Tools service in the virtual machine. VMware recommends using NTPD or Chrony in Linux-based operating systems and W32Time for Microsoft Windows. For more information, see Timekeeping best practices for Linux guests and Timekeeping best practices for Windows, including NTP and Disabling Time Synchronization.|
|Unable to access the virtual machine configuration: Unable to access file [<Datastore>] <file>.||See the VMware article to determine the cause of the error and its resolution.|