Single-site deployment is appropriate if your infrastructure – machines and instances on multiple hosts – can be successfully hosted and maintained on a single network location. In this case, you need to install both the Director and Transporter on a single machine within your infrastructure.
If your infrastructure segments are separated by a WAN, you will have to apply multi-site deployment. In this case, you will have to install the Director and Transporter on one site, and at least one Transporter on all other sites of your infrastructure.
Using multi-site deployment, you can apply different settings for each site – such as backup repository compression ratio, retention policies, and bandwidth rules – thus, obtaining great flexibility in managing your infrastructure.
With multiple Transporters deployed, network acceleration and AES 256 traffic encryption can be enabled between the Transporters. The Transporters optimize network traffic and improve data transfer speed. For more information, refer to the corresponding User Guide articles:
- Adding Installed Transporters
- Deploying Transporter as VMware Appliance
- Deploying Transporter as Nutanix Appliance
- Deploying Transporters in AWS EC2
- Managing Transporters
The following requirements must also be met to allow communication between the Director and Transporters in multi-site deployment:
- Corresponding TCP ports must be open with firewall software to enable communication between Director and Transporters, and between different Transporters.
- Corresponding TCP ports must be open with firewall software to enable communication between Director/Transporter and hypervisors' infrastructure.
For detailed requirements related to single-/multi-site deployment, you can refer to System Requirements.