• If a virtual CD or DVD ISO is not available on the host where you restore the virtual machine, the restore fails. The vCenter interface may include the following message:

  Invalid configuration for Device '1'.

• If the virtual machine to restore and the virtual machine that contains the hotadd restore host do not reside in the same data center, the restore fails.

• The restore host cannot access the VMware datastore over the selected transport mode. The job log on the restore host may contain messages like the following example:

  FTL - Virtual machine restore: VxMS initialization failed.

• You attempted to restore a file that has a path name longer than 1023 characters. A backup of a Linux virtual machine backs up all files, including those with path names longer than 1023 characters. But you cannot restore the long path-name files individually.

• For the restore, the virtual machine's hardware version (such as 7) is later than the hardware version that the target server supports. If VMware Tools cannot convert the virtual machine's hardware version to an earlier version, the restore fails. Messages similar to the following appear in the detailed status log:

  Info bpVMutil(pid=6268) INF - vmwareLogger: WaitForTaskCompleteEx: 
  The virtual machine version is not compatible with the version of the 
  host <hostname>.

• You attempted to restore a large virtual machine with one or more VMDKs that are formatted as Thick Provision Eager Zeroed. Because of the size of the virtual machine or its VMDKs, creation of the virtual machine may take more than 2 hours. As a result, the restore failed.

Check the job details in the Activity Monitor and take action as dictated by that information, as follows:

• Ensure that an .ISO file that is presented to a virtual machine as a virtual CD or DVD during backup is available on the destination host.

• For a successful hotadd restore, ensure that the two virtual machines are in the same VMware data center.

• Select a different transport mode and retry the restore.

• You cannot restore restore a file that has a path name longer than 1023 characters.

• If possible, restore the VM to a VMware server that supports the VM's hardware version.

• In Backup, Archive, and Restore, change the restored virtual disk to Thick Provision Lazy Zeroed or Thin Provisioning.

When a VMware agentless restore is performed, the restore can cause one of the following issues:

• Failed to identify the newly attached device on destination VM %s. One possible cause is that the destination VM user credentials have insufficient permissions.

  It is recommended target VM user credentials with root or administrative privileges.

• Failed to attach the temporary vmdk %s to the destination VM %s with error %d.

  Make sure that the target VM has at least one paravirtual controller with available LUNs.

• Failed to upload the process rename file to the destination VM %s with error %d.

  Make sure there is sufficient space available in target VM.

• Failed to restore the selected files and folders.

  Review the tar log to troubleshoot this issue.