What is the Transporter?
The Transporter is the product component that does all of the heavy-lifting: it performs backup, replication, and recovery, as well as data compression, deduplication, and encryption.
An instance of the Transporter is automatically installed along with the Director to enable backup, replication, and recovery out of the box. The default Transporter is called “Onboard Transporter” and cannot be removed from the product.
A single Transporter can back up, replicate, and recover multiple VMs and cloud instances, for example:
One Transporter can simultaneously process multiple source disks (6 by default) during backup, replication, and recovery. If jobs contain more disks than the Transporter is set to process simultaneously, the disks will be put in a queue and will be processed once the Transporter frees up.
How Many Transporters should be Deployed
In most cases, it is sufficient to deploy only one Transporter per site. In large environments, where multiple source items should be processed simultaneously, multiple Transporters can be deployed to distribute the workload, for example:
Deploying multiple Transporters also enables network acceleration and AES 256 encryption of traffic between a pair of Transporters. For example, if VMs are replicated over WAN between two sites, the Transporter installed in the source site can compress and encrypt data before transferring it over WAN, and the Transporter installed in the Target site can unencrypt and decompress the data prior to writing it to the target server, for example:
If you plan to transfer data over WAN without a VPN connection from your source site to the target site, make sure the source and target Transporters are added to the product using external IP addresses or using DNS names that can be properly resolved in WAN (so the two Transporters can connect to each other).
How Transporters are Selected for Jobs
In large and geographically distributed environments multiple Transporters can be deployed to distribute the data protection workload, optimize network traffic, and improve data transfer speeds. Thus, if more than one Transporter is deployed for NAKIVO Backup & Replication, it is important to determine which one should be used to read data from a particular source and which one should be used to write data to a target.
By default, the product automatically determines which Transporter should be used based on proximity of a Transporter to the source or target server. The proximity is measured by using the ping round trip time, for example:
In the example above, Transporter 1 will be selected to read data from the Source ESXi, and Transporter 2 will be selected to write data to the Target ESXi.
The Transporter selection can also be configured manually during the job creation.
Transporter as VMware Appliance
NAKIVO Onboard Transporter may not support VMware. This is the case for application deployment on an ARM-based NAS because some functionality necessary for working with VMware is missing for such devices.
In this case, you will need to deploy an additional Transporter as a VMware appliance to allow the application to work with VMware vCenters and ESXi hosts, and protect your virtual infrastructure.
When deployed, the additional Transporter allows the application to retrieve necessary data via Transporter-to-Transporter communication.