Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


VMware VM processing fails. The following error message appearsis displayed:

Code Block
Hot Add transport mode cannot be used by the transporter to access one or more disks of this VM.


In order for the Hot Add to work, the source Transporter (the one reading data from the source VM) should have access to all datastores of the source VM.
Another important requirement is having the source Transporter VM present in the NAKIVO Backup & Replication inventory.

NOTE: If Hot Add cannot be enabled for at least one disk of a source VM (even if this disk is excluded in from the job), Hot Add may be unavailable for the entire VM.

Possible Cause

Transporter VM


Is Not in the Inventory

In order for Hot Add to function properly, the Transporter VM must be present in the Inventory.
To solve this issue, please add the vCenter or ESXi host where NAKIVO Backup & Replication Transporter VM is running , to the Inventory.

Transporter VM is in a Different Datacenter

If NAKIVO Backup & Replication Transporter VM and the source VM are in a different datacenterdatacenters, Hot Add will not be functional (even if there is a shared datastore).
To solve this problem, please deploy another Transporter VM in the same datacenter and select it in the job settings.


Hot Add is not possible for VMs with IDE disks. If your source VM contains an IDE disk, Hot Add mode will not be applicable for the entire VM.
To solve this problem, please  convert your virtual IDE disks into SCSI disks or process such VM by a separate job in LAN or SAN mode.


If NAKIVO Backup & Replication Transporter VM and the source VM have the same BIOS UUID, Hot Add will not be functional.
To solve this problem, please deploy another VM with a Transporter that has a different BIOS UUID, and use it to back up your VM(s).


Starting from NAKIVO Backup & Replication v7.5, TLS 1.0 which that is used by ESXi 5.5, is not supported by default.
We recommend updating your vSphere environment to the latest version to avoid usage of the old TLS.

If this solution is not available, please create a configuration file on the machine where on which the source Transporter is installed: