Skip to content

Resilio Active Everywhere takes too much space on disk

Both main Resilio Active Everywhere components - Agent and Management Console - may take up significant amount of storage space. Review the information below if any of these components start consuming more space than you expect.

Shut down before deleting

Before deleting any files listed in this topic, make sure to shut down the relevant Agent or Management Console first.

Resilio Agent

On hosts running Resilio Agent, you may find excessive storage occupied by the archive folders or the storage folder.

Archive folders

Every folder where Agent delivers data contains a dedicated archive folder. Therefore, if you notice that a shared folder takes more space than expected for synchronized files, this is most likely due to the Archive. You can either manually delete files from the Archive, provided you acknowledge that you won't be able to restore them, or you can change the Archive settings in Agent Profile for it to rotate faster. Alternatively, you can enable Transparent Selective Sync on macOS or Windows to free up space occupied by unnecessary files.

Storage folder

The exact location of the Agent's storage folder varies, for details see Storage folder. The majority of space can be consumed by:

  • Database files
    Agent keeps a record of all file and folder entries in the share, both currently present and deleted. So the more files are or have been in the share, the bigger the database gets: pre-3.x versions require around 2 KB per file and each subfolder in its path. Size may double when syncing either NTFS or Posix permissions depending on the number of ACLs applied per file. Versions 3.x and newer require around 256 bytes per file/subfolder.

!!! warning

  It is not safe to delete databases manually and doing so may result in data loss. Agents automatically clean up unused databases when they are removed from the Job, or when the Job is deleted.

  • Debug log files
    These are sync.log and sync.log.####.zip files where #### is a timestamp. Default log rotation scheme: each 100 MB (1 GB in version 2.11) of log is zipped up and stored for 7 days, with no more than 100 zip files stored. These zip files can be deleted safely provided you won't need them for troubleshooting. You can also disable debug log recording in your Agent profile by setting the Debug logging parameter to No.

  • Event logs
    Stored in the events folder. Agent automatically cleans up events once they are uploaded to Management Console. Can be safely removed if you don't need the events generated by the Agent.

  • Upgrade backup folder
    Stored in the sync-v<version>-<timestamp>.backup subfolder, like sync-v2.8.3-1585924821.backup. Only created during an upgrade; can be safely deleted without an Agent restart or shutdown.

  • Client history cache
    The clienthistorycache folder stores files containing system events collected by the Agent for system and performance monitoring purposes, and transferred to the Management Console. By default, Agents upload events that are not older than two days (172800 seconds). To adjust the default value, add the mc_events_ttl custom parameter to the Agent Profile with a value (expressed in seconds) better suited to your deployment. You can delete the files in the folder, but don't delete the ones for the current day.

The rest of the files in the storage folder do not consume significant amount of space and are not recommended to be deleted, as deletion may cause unexpected negative effects.

Management Console

Most of the space is taken by the storage folder. Here is the breakdown for the largest file groups:

  • Debug logs
    Inside the /data subfolder: all common*.log, w*-common.log, db*.log, and db-history*.log files. These files can be deleted safely provided they're not needed for troubleshooting. These files rotate automatically and the rotation rules are controlled by the loggers section of the Management Console's configuration file.

  • Audit log file
    audit*.log grows slowly under normal conditions, but intensive API usage can cause it to expand rapidly. It can be safely removed and its rotation is governed by the same loggers section of the Management Console's configuration file as the debug logs.

  • Support requests
    The data/clients-logs and data/logs-temp subfolders store the debug logs you've collected through the support request form in the Management Console. Don't delete these files if a support request is being created at the moment.
    Subdirectories in the /support_requests folder. The Management Console only retains requests that were not delivered to Resilio. It is safe to clean the content of this folder if you don't have any ongoing support requests with Resilio, Inc.

  • Reporting
    Contains events from Agents and statistical data for graphs. Can be deleted safely. The amount of data stored for reporting purposes is controlled via the reporting section of the Management Console's server configuration file.

  • Server backup
    Management Console generates a backup on a daily basis. Backup frequency can be changed in the [Management Console's server configuration file] (for details, see Change backup frequency). Server backups are also safe to delete.