Both main Resilio Connect components - Connect Agent and Management Console - may take some space on a disk. Please review the information below if any of these components start consuming more space than you expect.
Shut down before deleting anything
If the text below states "safe to delete" please take care to shut down relevant Agent or Management Console first.Resilio Agent
You may find excessive space spend by 2 main consumers: archive folders and storage folder.
Archive folders
Every folder where Agent delivers data has an archive folder next to it. Therefore if you notice that a shared folder take more space than it's expected to be taken by synced files, most likely it's Archive. You can either manually delete files from Archive provided you acknowledge that you won't need to restore them. Also, you can change Archive settings for it to rotate faster. Alternatively, it's possible to make use of transparent selective sync on macOS or windows to clear off unnecessary files.
Storage folder
Exact location of agent's storage folder varies, find the full reference here. The majority of space can be consumed by:
- Database files.
Agent keep record of all file and folder entries in the share, currently present and deleted. So the more files are or have been here, the bigger database is: pre 3.x version require around 2 KB per file and each subfolder in its path. Size may may double when syncing either NTFS or Posix permissions depending on the number ACLs applied per file. Versions 3.x and newer require around 256 bytes per file/subfolder. It is NOT SAFE to delete databases manually and may cause data loss. Agent automatically cleans up unused databases when it's removed from the job, or if the job is deleted from MC. - Debug log files.
These are sync.log andsync.log.####.zip
files where #### is a timestamp. Default log rotation scheme: each 100Mb (1Gb in version 2.11) of log is zipped up and is stored for 7 days, no more than 100 zip files are stored. These zip files can be deleted safely provided you're not going to troubleshoot with support team. You can also disable debug logs recording in your Agent profile by setting "Debug logging" parameter to "No". - Event logs.
Stored in folder events. Agent automatically cleans up events once uploaded to Management Console. Can be safely removed if you don't need the events generated by the agent. - Upgrade backup folder.
Stored insync-v<version>-<timestamp>.backup
subfolder, likesync-v2.8.3-1585924821.backup
. Only created during the upgrade, can be safely deleted without agent restart or shutdown.
The rest of files in storage folder are not consuming any significant space and not recommended to be deleted as the deletion may cause various negative effects.
Management Console
Most of the space is taken by storage folder. Here's the breakdown for the largest file groups:
- Debug logs
inside the/data
subfolder, all thecommon*.log
,w*-common.log
,db*.log
,db-history*.log
These files can be deleted safely provided you're not going to troubleshoot with support team. These files rotate automatically and the rotation rules are controlled by "loggers" section of the server configuration file. - Audit log file.
audit*.log
usually grows slowly but can start growing really rapidly with intensive API usage. Also can be removed safely and controlled by same section as debug logs files. - Support requests
subdirectoriesdata/clients-logs
anddata/logs-temp
, provided you're not troubleshooting with support now. These subdirectories keep the debug logs you've collected through support request form in MC. Don't delete these files if a support request is being created at the moment.
subdirectory in/support_requests
folder. MC only leaves the requests that were not delivered to Resilio automatically for some reason. It is safe to clean the content of the 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. Amount of data stored there is controlled by MC server configuration file, "reporting" section. - Server backup
Management Console generates backup on a daily basis. Backup frequency can be controlled with configuration file, too. See the "backup" section. Server backups are also safe to delete.