Resilio Connect is a distributed file delivery solution based on peer-to-peer topology, but as the same time it offers a number of ways to shape the connectivity matrix of the Agents to achieve the best results for a particular use case. Below is the overview of possible options.
Default configuration with Tracker and LAN discovery
By default Resilio Connect relies on Tracker server for peer discovery. All Agents in a job connect to the configured Tracker and then to each other. This solution allows to connect as many Agents together as possible, provided there's direct Agent-to-Tracker and Agent-to-Agent connection. Default configuration involving Tracker server suits the setup with large number of Agents that need to exchange the files with each other in a timely manner.
Additionally Agents use LAN multicast and broadcast packets to discover each other in LAN.
Read more about Tracker here and about standard peer discovery flow here.
Read more about Tracker here and about standard peer discovery flow here.
Pros:
+ all Agents will try and connect to all Agents in the job, facilitating file exchange
+ does not require any additional configuration, works out of the box
+ tracker server can be placed anywhere in the network
Cons:
Cons:
- requires direct network tunnel between Tracker and each of the Agents, as well as between the Agents themselves
- more system resources are used on the Agent host as the Agent is trying to establish multiple connections
- number of Agents that can be connected together to each other at the same time is limited by 50 Agents. This number can be configured though.
- more system resources are used on the Agent host as the Agent is trying to establish multiple connections
- number of Agents that can be connected together to each other at the same time is limited by 50 Agents. This number can be configured though.
Known hosts
Known hosts - is a parameter in the Agent Profile that tells the Agent where to connect directly, skipping the tracker server. With known hosts Admin can control which of the Agents connect, and which - don't. For example, endpoints need to connect to a central server, but not to each other. Overall, this configuration suits small setups where admin defines known host for 1 or 2 machines or setups with unstable MC connectivity.
Read more about this configuration here.
Pros:
+ easy to understand and setup
+ can use both DNS name and IP address
+ independent from any Agent discovery mechanism, therefore can target any addresses
Read more about this configuration here.
Pros:
+ easy to understand and setup
+ can use both DNS name and IP address
+ independent from any Agent discovery mechanism, therefore can target any addresses
Cons:
- does not support Resilio Proxy
- requires manual correction in case of IP change or DNS change, same reason makes it less robust
- must be agent-and-job perfectly configured otherwise Agent will waste system resources with redundant connections
- makes your setup dependent on a single agent that has known hosts configured
- does not support Resilio Proxy
- requires manual correction in case of IP change or DNS change, same reason makes it less robust
- must be agent-and-job perfectly configured otherwise Agent will waste system resources with redundant connections
- makes your setup dependent on a single agent that has known hosts configured
Resilio Proxy
Proxy server can be used in restricted network environment that does not allow incoming connections.
Read more about configuring and using Proxy here.
Read more about configuring and using Proxy here.
Pros:
+ overcomes network restrictions
+ ensures data safety and integrity
+ allows direct connection between hosts if it's possible
Cons:
- reduces data transfer speed since all the traffic is relayed through proxy
- reduces data transfer speed since all the traffic is relayed through proxy
- requires proper configuration of Proxy connections on MC
Network policy
Overall Network policy suits larger setups with 10+ Agents and in case where system shall automatically decide which Agent from a swarm connects to a central Agent another swarm. It also allows to control the number of possible connections between swarms.
Read more about configuring network policy here.
Pros:
+ Resilio Connect automatically builds and re-builds connectivity matrix if anything in the networking changes (this is also a disadvantage).
Read more about configuring network policy here.
Pros:
+ Resilio Connect automatically builds and re-builds connectivity matrix if anything in the networking changes (this is also a disadvantage).
+ makes whole setup more robust due to automatic agent election
+ saves agent resources by preventing redundant connections
+ works with Resilio Proxy
Cons:
- Resilio Connect automatically builds and re-builds connectivity matrix if anything in the networking changes, which add extra load on Management Console to recalculate and on Agents and to re-establish connections
- Tracker connectivity is a must
- more complex setup requiring proper tagging of Agents
+ saves agent resources by preventing redundant connections
+ works with Resilio Proxy
Cons:
- Resilio Connect automatically builds and re-builds connectivity matrix if anything in the networking changes, which add extra load on Management Console to recalculate and on Agents and to re-establish connections
- Tracker connectivity is a must
- more complex setup requiring proper tagging of Agents