Articles in this section

System requirements

Operating system

Windows (x64)

  • Windows 8.1 or newer
  • Windows Server 2012 R2 or newer

Linux (x64)

  • kernel 4.18 or newer
  • glibc 2.28 or newer

Ubuntu

  • 16.04 or newer

CentOS

  • glibc 2.28 or newer
For information on how to check if your system meets the requirements, see How to check system requirements for the Management Console installation.

3.x requirements

Windows (x64)

  • Windows 8.1 or newer
  • Windows Server 2012 R2 or newer
    Note: Resilio Active Everywhere 3.6.0 does not support Windows Server 2012.

Linux (x64)

  • kernel 4.18 or newer (applicable to Resilio Active Everywhere 3.6 and newer)
  • glibc 2.28 or newer (applicable to Resilio Active Everywhere 3.6 and newer)
  • kernel 2.6.32 or newer
  • glibc 2.17 or newer
  • GCC 5.1.0: libstdc++.so.6.0.21
  • GCC 5.1.0: GLIBCXX_3.4.21, CXXABI_1.3.9

Ubuntu

16.04 or 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.

 

2.x requirements

Windows (x64)

  • Windows 7 or newer
  • Windows Server 2008 R2 or newer

Linux (x64)

  • kernel 2.6.32 or newer
  • glibc 2.17 or newer
  • GCC 5.1.0: libstdc++.so.6.0.21
  • GCC 5.1.0: GLIBCXX_3.4.21, CXXABI_1.3.9

Ubuntu

16.04 or newer

 

Web interface

  • Most internet browsers
  • Internet Explorer, version 11
    Note: Support has been removed in Resilio Active Everywhere 4.1.

Hardware requirements

Deployment size CPU System memory Storage
50 Agents
10 jobs each		 Intel Core i5 7600 or similar,
4 cores		 6 GB SSD
400 MB/s
100 Agents
50 jobs each		 Intel Core i5 7600 or similar,
4 cores		 8 GB SSD
400 MB/s
1,000 Agents
300 sync jobs each		 Intel Core i7 10700 or similar,
8 cores		 10 GB NVME
1500 MB/s

10,000 Agents
750 jobs total

 Intel Core i7 13700 or similar,
16 cores		 32 GB NVME
1500 MB/s

Additional 2 GB or RAM is required to build a files' report in a Distribution or a Storage Tiering job. The RAM is freed once the report is built.

Minimum hardware configuration for 10 Gbps throughput:

CPU 4-6 cores or more (twice as many if deployed on a Virtual Machine), 3 GHz minimum base frequency.
System memory 16 GB or more (in addition to files-based requirements listed above).
10 Gbps minimum memory bandwidth throughput.
Storage 1250 MB/s sustained read/write performance
Network 10 GbE (for example Intel X520, X540, Mellanox ConnectX series)
An external network interface must be connected to a PCIe Gen3 x8 slot or higher.

Storage space requirements

Total storage space required is the sum of space taken by: 

  • Job runs database - Taking approximately 4MB per 100 job runs.

  • Backup archives - Taking as much space as the job runs database multiplied by the number of backups (see here for more details about backups).

  • MC logs - Logs rotate as the log file reaches 100 MB when the log file is zipped. No more than 10 log files are kept (this value can be changed in the MC configuration file).

  • System and file events - Storage space taken up by system and file events depend on the size of your deployment and the activity it generates. The table below provides approximate storage space and system memory usage for different deployment scenarios. By default, events are rotated every 14 days.

Deployment size

Storage

System memory 


 

All events

File events

50 agents, 10 sync jobs, 1000 files each, updated several times per hour

400 MB per day
+ errors

5.9 GB

900 MB

200 agents, 5 sync jobs each, 1000 files each job, updated several times per hour

 800 MB per day + errors

50 GB

1.2 GB

10 agents, transfer 1 to 9, 100 files and a post_download script, started hourly

60 MB per day
+ errors

41.3 MB

76 MB 

100 agents, transfer 1 to 99, 100 files and a post_download script, started hourly

600 MB per day
+ errors

395 MB

140 MB

100 agents, transfer 99 to 1, 2000 files and pre-indexing script, 12 runs per day

 statistically insignificant

2.2 GB

1.26 GB

1000 agents, transfer 999 to 1, 2000 files and pre-indexing script, 12 runs per day

 statistically insignificant

9.8 GB

2.02 GB

5 agents all RW with peer-2-peer enabled, 1 sync job, 20 million files with 1000 files updated hourly.

 statistically insignificant

12 GB

1.68 GB

3 agents all RW with peer-2-peer enabled, 1 sync job. 10 million files with 1000 files updated hourly. Enabled NTFS permissions by group.

 statistically insignificant

10 GB

1.8 GB

2 agents, 1 distribution job, 20 million files transferred in batches of 100k files.

 statistically insignificant

500 MB

1.75 GB

 

 

Operating system

Windows

  • Windows 7 or newer (x64)
  • Windows 10 or newer (ARM) (compatible with Resilio Active Everywhere 4.1 and newer)
  • Windows Server 2008 R2 or newer
  • Agent UI: IE11 or newer (available in Windows 7 SP1 and newer)
  • Additional requirements apply to Transparent Selective Sync (TSS). For details, see Transparent Selective Sync (TSS) on Windows.

macOS

  • macOS 10.15 (Catalina) or newer for Resilio Agent 4.2.2 and older.
  • macOS 12 (Monterey) or newer for Resilio Agent 4.2.3 and newer.
    Note: macOS 15 (Sequoia) requires Resilio Agent 4.0.5 or newer.
    Note: macOS 26 (Tahoe) requires Resilio Agent 4.2.3 or newer.
  • Additional requirements apply to Transparent Selective Sync (TSS). For details, see Transparent Selective Sync (TSS) on Windows.

Linux

  • i386
  • x64
  • ARM64
  • glibc 2.17 and newer 

FreeBSD

FreeBSD 11 or newer

Android

Android 4.2 or newer

NAS

  • Synology
    Note: Support for NAS packages with arm-based installers (ARM, ARMhf, ARMel, ARMv7) has been removed in Resilio Active Everywhere 4.0.
  • QNAP
  • WD NAS

3.x

Windows

  • Windows 7 or newer (x64)
  • Windows 7 or newer (x86) (compatible with Resilio Active Everywhere 3.7 and older)
  • Windows Server 2008 R2 or newer
  • Agent UI: IE11 or newer (available in Windows 7 SP1 and newer)
  • Additional requirements apply to Transparent Selective Sync (TSS). For details, see Transparent Selective Sync (TSS) on Windows.

macOS

  • macOS 10.15 (Catalina) or newer.
    Note: macOS 13 (Ventura) requires Resilio Active Everywhere 3.4.1 or newer.
  • Additional requirements apply to Transparent Selective Sync (TSS). For details, see Transparent Selective Sync (TSS) on Windows.

Linux

  • i386
  • x64
  • ARM64, ARM, ARMhf, ARMel, ARMv7, ARMv5 (ARMv5 support available in Resilio Active Everywhere 3.7 and older)
  • glibc 2.6 or newer (applicable to Resilio Active Everywhere 3.8 and newer)
  • glibc 2.3 or newer (applicable to Resilio Active Everywhere 3.7 and older)

FreeBSD

FreeBSD 11 or newer

Android

Android 4.2 or newer

NAS

  • Synology
    Note: Synology 88f6281 package architecture had been deprecated in Resilio Active Everywhere 3.8.
  • QNAP
  • WD NAS
  • Drobo

 

macOS

Windows

  • Windows 7 or newer (x64)
  • Windows 7 or newer (x86)
  • Windows Server 2008 R2 or newer
  • Agent UI: IE9 or newer
  • Additional requirements apply to Transparent Selective Sync (TSS). For details, see Transparent Selective Sync (TSS) on Windows.

macOS

  • 10.15 Catalina or newer
    Note: The M1 chip support is available in Resilio Active Everywhere 2.12 and newer.
  • Additional requirements apply to Transparent Selective Sync (TSS). For details, see Transparent Selective Sync (TSS) on Windows.

Linux

  • i386
  • x64
  • ARM64, ARM, ARMhf, ARMel, ARMv7, ARMv5
  • glibc 2.3 or newer

FreeBSD

FreeBSD 11 or newer

Android

Android 4.2 or newer

NAS

  • Synology
  • QNAP
  • WD NAS
  • Drobo

2.x

Windows

  • Windows 7 or newer (x64)
  • Windows 7 or newer (x86)
  • Windows Server 2008 R2 or newer
  • Agent UI: IE11 or newer (available in Windows 7 SP1 and newer)
  • Additional requirements apply to Transparent Selective Sync (TSS). For details, see Transparent Selective Sync (TSS) on Windows.

macOS

Linux

  • i386
  • x64
  • ARM64, ARM, ARMhf, ARMel, ARMv7, ARMv5
  • glibc 2.3 or newer

FreeBSD

FreeBSD 11 or newer

Android

Android 4.2 or newer

NAS

  • Synology
  • QNAP
  • WD NAS
  • Drobo

 

macOS

Windows

  • Windows 7 or newer (x64)
  • Windows 7 or newer (x86)
  • Windows Server 2008 R2 or newer
  • Agent UI: IE9 or newer
  • Additional requirements apply to Transparent Selective Sync (TSS). For details, see Transparent Selective Sync (TSS) on Windows.

macOS

  • 10.15 Catalina or newer
    Note: The M1 chip support is available in Resilio Active Everywhere 2.12 and newer.
  • Additional requirements apply to Transparent Selective Sync (TSS). For details, see Transparent Selective Sync (TSS) on Windows.

Linux

  • i386
  • x64
  • ARM64, ARM, ARMhf, ARMel, ARMv7, ARMv5
  • glibc 2.3 or newer

FreeBSD

FreeBSD 11 or newer

Android

Android 4.2 or newer

NAS

  • Synology
  • QNAP
  • WD NAS
  • Drobo

Hardware requirements

System memory

Note: When estimating system memory size, make sure to take into account not only the Agent itself but also the operating system and other services running on it. The exact amount will vary depending on the system's workload and configuration.
The system memory used by Resilio Active Everywhere depends on the number of files being handled, with each file entry occupying:
  • 256 bytes of RAM in RAM-optimized jobs (applicable to Resilio Active Everywhere 3.0 and newer)
  • 2 KB of RAM (applicable to Resilio Agent 2.12 and older)
    Example: For 4.5 Million files up to 9 GB of RAM is required.
    Note: RAM requirements double when syncing NTFS or Posix permissions depending on the number ACLs applied per file. Use time window-based file monitor, to limit memory usage.

Note: Resilio Active Everywhere keep records of all deleted entries in the job. Each entry consumes RAM as well accordingly.

Storage space

Total storage space required is the sum of space taken by: 

  • Jobs database - Taking up a similar amount as the size the of system memory allocated to the Agent service.

  • Database backups - Created each time the Agent is updated to a new version.

  • Debug logs - Logs are rotated when the log file reaches 1 GB. At that point, the file is compressed. The system retains up to 100 log files.

Below are configuration examples, based on average load.

 

Based on the number of files

Note: The RAM size in the table below is the memory consumption estimate for the Agent service only.

Deployment size CPU System memory
< 100k files single core, ARM, x86, x64 512 MB
< 1M files 2 core, ARM, x86, x64 Less than 1 GB
> 1M files 4 core, ARM, x86, x64

Approx. 1 GB
~ 50M files 8 core, ARM, x86, x64

Approx. 12 GB
~200M files 16 core, ARM, x86, x64

Approx. 48 GB

 

2.x

Deployment size CPU System memory
< 100k files single core, ARM, x86, x64 512 MB
< 1M files 2 core, ARM, x86, x64 2 GB
> 1M files 4 core, ARM, x86, x64

4 GB
~ 50M files 8 core, ARM, x86, x64

95-100 GB.

 

Based on the expected transfer speed
Recommended hardware configuration for expected transfer speeds of up to 10 Gbps:

CPU Xeon E5 2600 v4 series or i7-7000 series, 4 cores or more (twice as many if deployed on a Virtual Machine), 2 GHz minimum base frequency.
System memory

16 GB or more (in addition to files-based requirements listed above)
10 Gbps minimum memory bandwidth throughput.
Network An external network interface must be connected to a PCIe 2.0 x4 slot.
Link aggregation shall be avoided.
For NUMA machines with select CPU slots empty, network card PCIe slot should connect to the occupied CPU slot.
Operating system Windows Server 2019 or newer.
Note: Non-server Windows versions cannot 10 Gbps performance.
Other platforms shall meet hardware requirements above. 
Storage Read/write speed over 1.2 GB/s.

 

Based on expected cloud storage performance

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 

Note: The RAM size in the table below is the estimated additional memory consumption that must be added to the per file memory consumption mentioned earlier.

Deployment Size CPU System memory Storage
> 2000 Containers 4 core or higher 8 GB

~300 MB/s as shown in the diagnostics section of the console.
3000~8000 Containers 8 core or higher 8 GB

500-700 MB/s as shown in the diagnostics section of the console.
Note: More than 8000 containers are supported but hardware requirements will need to be determined based on size and use case.

 

One-to-many use case (Distribution and Consolidation jobs)

Note: The RAM size in the table below is the estimated additional memory consumption that must be added to the per file memory consumption mentioned earlier.

Deployment size CPU System memory Storage
100 transfers 4 cores
  8 GB 2000+ IOPS
1000 transfers 8 cores or higher
 32 GB 10000+ IOPS

Tip: We recommend using the Optimize for low bandwidth preset.

Operating system

Windows (x64)

  • Windows 10 or newer (x64)
  • Windows Server 2008 R2 or newer

Linux (x64)

  • glibc 2.17 or newer

Minimum hardware requirements

Based on the number of files

Deployment Size CPU System memory
< 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

Note: The required system memory size depends on the number of agent connections (a single Agent may install several connections if it uses proxy for several jobs), distance between agents and proxy, and bandwidth between them. A minimum value is 1 Mb per connection. On 10 Gbps networks it may require 300 MB per connection.

Based on the expected transfer speed

Note: With indirect connection through a proxy, speed deterioration of up to 10% may be observed compared to direct tunnel between Agents.


Recommended hardware configuration for expected transfer speeds of up to 5 Gbps:

CPU

Xeon E5 2600 v4 series or i7-7000 series, 4 cores or more (twice as many if deployed on a Virtual Machine), 2 GHz minimum base frequency.
System memory

16 GB or more (in addition to files-based requirements listed above)

10 Gbps minimum memory bandwidth throughput.
Network An external network interface must be connected to a PCIe 2.0 x4 slot.
Link aggregation shall be avoided.
For NUMA machines with select CPU slots empty, network card PCIe slot should connect to the occupied CPU slot.
Operating system

Windows Server 2019 or newer.
Note: Non-server Windows versions cannot ensure 10 Gbps speeds.
Other platforms shall meet hardware requirements above. 

 

Related articles