OS
- Windows (64-bit only)
- 8.1 and newer (pre-3.0.0 support Windows 7 and newer)
- Windows Server 2012 R2 and newer (version 3.6.0 does not support WindowsServer 2012, pre-3.0.0 versions support Windows Server 2008 R2 and newer) - Linux x64
- kernel 4.4. and newer
- glibc 2.17 and newer
Versions older than 3.6.0 require
- kernel 2.6.32 and newer
- glibc 2.17 and newer
- GCC 5.1.0: libstdc++.so.6.0.21
- GCC 5.1.0: GLIBCXX_3.4.21, CXXABI_1.3.9
Read this article for instructions on checking library versions. - Ubuntu 16.04 and newer
- CentOS
Management console versions 3.4.x and 3.5.x require CentOS 8.0.1905 or newer. 3.6.x may run on older versions of CentOS.
WebUI
- Most Internet Browsers
- For Internet Explorer, version 11
Hardware requirements
| Deployment Size | CPU | RAM | Disk type |
| 50 Agents 10 jobs each |
Intel Core i5 or similar, 4 cores |
6 GB | SSD |
| 100 Agents 50 jobs each |
Intel Core i5 or similar, 4 cores |
8 GB | SSD |
| 1,000 Agents 300 sync jobs each |
Intel Core i7 or similar, 8 cores |
10 GB | NVME |
|
10,000 Agents |
Intel Core i7 or similar, 16 cores |
32 GB | NVME |
Storage space requirements
Total storage space required is the sum of space taken by job run database files, MC backups, logs (some static value as they rotate) and events.
All measurements are approximate for average load on the MC.
Job runs database requirement: around 4MB per every 100 job runs.
Each backup archive takes as much space as job runs database multiplied by the number of backups (see here for more details about backups).
MC logs rotate as the log file reaches 100 Mb, the log is zipped. No more than 10 log files are kept (can be changed in MC configuration file).
Below are the measurements for storage space taken by events.
(These are clean tests when MC is only busy with writing events - no reading events, no other heavy processes, etc. Also, events filters are not applied. Real life results may vary.
When measuring system load, in tiers marked as 1->n or n->1, MC agent is used as this “1” agent. Hardware: Intel® Core™ i7-3770 CPU @ 3.40GHz 28 GB DDR3 RAM)
|
Deployment Size |
STORAGE |
System Load on MC* |
|
|
All events |
File events |
CPU / RAM |
|
|
2 agents, 1 sync job, 100 files, updated several times per hour |
40 Mb per day |
31.7 MB |
3.2% / 200 MB |
|
10 agents, 1 sync job, 100 file updates per minute |
30 Mb per hour |
412 MB |
1.9% / 360 MB |
|
50 agents, 10 sync job, 1000 files each, updated several times per hour |
400 Mb per day |
5.9 GB |
30.27% / 900 MB |
|
200 agents, 5 sync job each, 1000 files each job, updated several times per hour |
50 GB |
38% / 1.2 GB |
|
|
10 agents, transfer 1 to 9, 100 files and a post_download script, started hourly |
60 Mb daily |
41.3 MB |
1.9% / 76 MB |
|
100 agents, transfer 1 to 99, 100 files and a post_download script, started hourly |
600 Mb daily |
395 MB |
2.1% / 140 MB |
|
100 agents, transfer 99 to 1, 2000 files and pre-indexing script, 12 runs per day |
statistically insignificant |
2.2 GB |
16.5% / 1260 MB |
|
1000 agents, transfer 999 to 1, 2000 files and pre-indexing script, 12 runs per day |
statistically insignificant |
9.8 GB |
47 % / 2.02 GB |
|
20 million files, 1 sync job. 5 agents all RW with peer-2-peer enabled. 1000 files is updated hourly. |
statistically insignificant |
12 GB |
6.5% / 1680 MB |
|
10 million files, 1 sync job. 3 agents all RW with peer-2-peer enabled. 1000 files is updated hourly. + enabled NTFS permissions by group |
statistically insignificant |
10 GB |
7.21% / 1800 MB |
|
20 million files, 1 dist job, 1 to 1 transfer. Transfer in batch by 100k files |
statistically insignificant |
500 MB |
9.3% / 1750 MB |
OS
- Mac OS X 10.15 Catalina or later
- M1 chip is supported starting from Resilio Connect version 2.12
- Mac OS 13 Ventura is supported starting from Resilio Connect version 3.4.1
- See requirements for TSS here - Windows
- 7 or later (64-bit). Support for 32-bit Windows is dropped with Resilio Agent version 3.8.0.
- Windows Server 2008 R2 or later
- See requirements for TSS here
- Agent UI - IE11 or newer (available on Win7SP1 and newer). Pre-3.0.0 Agent support IE9 and newer - Linux i386 (glibc 2.17* and newer)
- i386*
- x64
- ARM (support for armv5 is dropped with Resilio Agent version 3.8.0, minimal required is armv7)
- ARMHF - FreeBSD 11 and newer
- Android 4.2 and newer
- Synology, QNAP, Drobo, WD NAS (support for 88f6281 Synology package architecture is dropped with Resilio Agent version 3.8.0)
*Older glibc: starting with Resilio Agent 3.8.0 support for glibc2.3 and glibc2.4 is dropped, minimal required is glibc2.6.
Minimum hardware requirements
Based on number of files
| Deployment Size | CPU | Available RAM* |
| < 100k files | single core, ARM, x86 or higher | 512 MB |
| < 1M files | 2 core, ARM, x86 or higher | Version 3.0.0: less than 1 GB Previous version: 2 GB |
| > 1M files | 4 core, ARM, x86 or higher |
Version 3.0.0: around 1 GB Previous versions: 4 GB minimum. 2 KB per file with an option to limit memory usage by time window based file monitor |
| ~ 50M files | 8 core, ARM, x86 or higher |
Version 3.0.0: around 12 GB |
More than 8000 containers are supported but hardware requirements will need to be determined based on size and use case.
Based on expected speed of transfer
For expected speed of up to 10 Gbit, this is recommended hardware:
| CPU | Xeon E5 2600 v4 series or i7-7000 series, with 4 physical cores or more (double that on a VM). Minimal frequency 2GHz. |
| Memory | 16 GB or more (adds to files' based requirements above) Minimal memory bandwidth throughput of 10 GBps is required. |
| NIC | For extension cards, extension slot must support full 4 lines for PCIe 2.0. Link aggregation shall be avoided. For NUMA machines with some CPU slots empty, network card PCIe slot should connect to occupied CPU slot. |
| OS | For Windows OS, only Windows Server can provide such expected speed, Windows server 2019. Other platforms shall meet hardware requirements above. |
| Disk | Read/write speed more than 1.2 GB/s for speed of 10 Gbps |
Based on expected speed of cloud storage
| EC2 agent, <1 Gbit | t3.xlarge instance and below |
| EC2 agent, >1 Gbit | m5d.12xlarge instance and greater |
| Azure agent, <1 Gbit | D4s v3 instance and below |
| Azure agent, >1 Gbit | D14 v2 instance and greater Standard_F32s_v2 for speed up to 9 Gbps (same region to sync files between storages) |
| Google cloud, >3 Gbit | n1- standard-64 and greater (same region to sync files between storages) |
Profile Container use case
| Deployment Size | Hardware | Recommended storage performance |
| > 2000 Containers | CPU: 4 core or higher around 8Gb of RAM* |
~300 MB/s as shown in the diagnostics section of the console. |
| 3000~8000 Containers | CPU: 8 core or higher around 8Gb of RAM* |
500-700 MB/s as shown in the diagnostics section of the console. |
One-to-many use case
consolidating data from many Agents onto a central server, or distributing data from a central server to many other Agents
| Deployment Size | Hardware | Recommendations |
| 1000 transfers | 8 cores CPU, 10000 IOPS+ 32GB* (additionally to memory per file as mentioned below) |
Use preset "Optimize for low bandwidth" |
| 100 transfers | 4 cores CPU, 2000 IOPS+ 8GB* (additionally to memory per file as mentioned below) |
*Agent memory consumption
Resilio Agents v.3.0.0. require around 256 bytes of RAM per entry in RAM-optimized jobs.
Resilio Agents of previous versions consume approximately 2 KB of RAM per file (example: for 4.5 Million files Connect can consume up to 9 GB of RAM). Using time window based file monitor, you can limit memory usage.
Agents of all versions keep records of all deleted entries in the job. Each entry consumes RAM as well accordingly.
Memory consumption
Memory consumption may double when syncing either NTFS or Posix permissions depending on the number ACLs applied per file, for pre-3.0 versions.Storage space requirements
Total storage space required is the sum of space taken by jobs database files, backups created after update, logs (some static value as they rotate) and events.
All measurements are approximate for average load on the MC.
Jobs database requirement:
Pre 3.0 Agents verisons require around 2 KB per file and each subfolder (or 4 KB of file permissions are synced), in each of Synchronization job. For example, two sync jobs, one has 1mln and the other - 3 mln files, will take up to 8 GB of storage , or up to 16 GB if file permissions are synced.
Version 3.0 and newer require around 256 bytes per entry in RAM-Optimized jobs.
On each update, the Agent creates backup folder with database files.
Debug logs rotate as the log file reaches 1 Gb, the log is zipped. No more than 100 log files are kept.
OS
- Windows 10 or later (64-bit);
- Windows Server 2008 R2 or later;
- Linux x64 (glibc 2.17 and newer)
Minimum hardware requirements
Based on number of files
| Deployment Size | CPU | Available RAM* |
| < 100,000 files | single core | 512 MB |
| < 1,000,000 files | 2 core or higher | 2 GB |
| > 1,000,000 files | 4 core or higher | 4 GB minimum. 2 KB per file with an option to limit memory usage by time window based file monitor |
Based on expected speed of transfer
Note: with indirect connection through a proxy speed deterioration of up to 10% may be observed compared to direct tunnel between Agents.
For expected speed of 5 Gbps, this is recommended hardware:
| CPU | Xeon E5 2600 v4 series or i7-7000 series, with 4 cores or more. Minimal frequency 2GHz. |
| Memory | 16 GB or more (adds to files' based requirements above). Minimal memory bandwidth throughput of 10 GBps is required. |
| NIC | For extension cards, extension slot must support full 4 lines for PCIe 2.0. Link aggregation shall be avoided. For NUMA machines with some CPU slots empty, network card PCIe slot should connect to occupied CPU slot. |
| OS | For Windows OS, only Windows Server can provide such expected speed, Windows server 2019. Other platforms shall meet hardware requirements above. |
*Proxy memory consumption
RAM requirements are in direct dependency from the number of connections (a single Agent may install several connections if it uses proxy for several jobs), distance between agents and proxy and bandwidth between them. Minimal value is 1 Mb per connection. On 10 Gbps networks it may require 300 MB per connection.