Resilio Connect 3.0.0 comes with major core changes, which are transparent to Resilio Admin, but still make new version pretty different from previous ones. Please review the paragraphs below before updating Resilio Connect.
New custom parameter to control memory usage
Starting with Resilio Connect 3.8.2. new parameter CUSTOM_MEMORY_LIMIT must be used to change the default value for possible RAM usage limits. Read more about it here.
Changes in system requirements
Starting with Resilio Connect 3.8.0 system requirements for Resilio Agent have changed. It’s no longer supported for Windows_x86 and FreeBSD_x86 platforms, requirements for arm and glibc were elevated. Please review latest system requirements for Agents here.
New port forwarding is required for MC
Support for MC API gateway is available in Resilio Connect v3.8.0. It’s enabled by default for new installations and can be enabled manually for updated MC. In either case for it to work port 8446 over TCP must be open and forwarded. Read the latest port forwarding requirements here.
Path validation on Windows Agents
New validation for symbols unsupported by the Windows OS. Job paths containing such symbols cannot be used in the job.
Changes in license information layout
This is the UI change in the License Administration.
New error messages
Rearranged some of the error messages reported by the Agent in a job. See change log for the new errors and events.
Planning the upgrade to 3.6.0?
Because of the advanced security configuration in 3.6.0, MC must be updated before Agents. Be sure to configure the same encryption key for the cluster nodes in Windows cluster setup. Otherwise the Agent won't be authorized on the MC after the cluster failover.
Sensitive data encryption
Agents v3.6 encrypt sensitive data in their settings files by default using hardware means or environment variables. Read more about it and its known limitations and peculiarities here.
MC can be configured to encrypt the database files after the update.
Got more than 500 agents?
Upgrade the Management Console first. Before update check that the number of MC sub-processes that perform the heavy load tasks (workers) is optimal for the number of Agents connected to the MC. Read here for more details. Agents shall be updated only after MC. Agents v3.0 are not compatible with MC of previous version.
Using API for a long time?
Check if you have outdated API tokens which are not supported by MC 3.6 and newer. Those tokens can be distinguished by its length - they are short (20 bytes). Delete the old token and generate a new one.
Support for Windows7 for the Management Console is deprecated
Starting with v3.0.0 MC can be installed on Windows 8.1 or newer, and Windows Server 2012R2
Support for IE9 and 10 for the Agent UI are deprecated
Agent UI version 3.0 requires IE11 on Windows OS
Parameter "Abort job run for offline agents" in Job Profile is deprecated
Instead, new functionality to abort a job run on an Agent was implemented in 3.4.0. The mentioned parameter is now moved to the Error Management section. See here for more details.
Iterative transfer of millions of files is deprecated
Resilio Connect v3.0.0 has greatly reduced RAM consumption and thus, no longer requires transferring the millions files in batches so as to fit the available ram (per this guide). Parameter transfer_job_files_limitis deprecated and is no longer supported.
Review your Job profiles and check if any of them that has this parameter is used in an active Distribution job. If so, postpone update until all files are transferred or contact Resilio Support team to have the jobs updated properly.
Introduced a Reference Agent for pre-seeded synchronization jobs
A Reference Agent must be selected for jobs that are configured to synchronise file permissions. Permissions inheritance will be disabled on all other Agents in the job, and the permissions will be overwritten with those from the Reference Agent. Read more about it here.
Not all files are uploaded to main server cannot stop the Agent from quitting
The Agent does not inform about pending upload queue and thus won't give warning about not all files uploaded to main server on quitting. This may be resolved by adding custom parameter merge_full_availability with value true in Job Profile before updating.
Core dumps can be enabled and buffer size can be increased by default with a script on Linux machines. The script is delivered in the tarball and shall be started manually if necessary.
Syncing NTFS permissions to Cloud / Linux / Mac Agents?
Ensure your Windows agents are running as Local System or contact Resilio Support to tweak default owners for files that were created on non-NTFS OSes.
Your users love to rename files/folders changing letter case OR using diacritic signs in filenames?
Ensure to enable Resolve filesystem name conflicts resolution on the Agent Profile.
Also, Resilio Connect v3.0.0 has a lot of changes in a way MC and Agent calculate and reflect jobs' performance metrics and statistics. Below are the expected changed that can be noticed
Updated main overview, job run and agents in job run overview.
Alerts were removed from main tab OVERVIEW and from daily/weekly subscription. Instead, Resilio Connect shows number of files and files synced, traffic saved, which gives a better understanding of Resilio's value.
Overview of job runs' and agents' in job runs were redesigned and populated with new information. Read more about these here.
Active files tab is empty when job in progress
Now, this tab contains only those files that the Agent is actually downloading at the given moment. It is OK that the tab might be empty even if you know that there are some files difference. It means that the Agent is not downloading them at this very moment. Refresh the page or visit it later.
Reference Agent cannot be removed from an already configured job
Reference Agent is still not compulsory for job that are not syncing file permissions. But if it was selected and job was saved, Admin cannot remove it anymore.
Remastered flow to ignore and error and abort job run on an error.
Previously the ignoring and aborting was applied to all agents by default and Admin needed to select exceptions. Now Admin will need to choose jobs and agents that will ignore the error or abort the job run. Updates shall be processed correctly and exceptions be reverted to selected jobs and agents.
Deprecated jobs_exceptions and agents_exceptions parameters in API
Caused by the remastered flow mentioned above.
SMTP configuration prompts
Now, if Admin tries to setup an email notification, dialog to configure SMTP appears, if the SMPT connection was not yet set up.
Events from History in Agent UI may disappears after update
Additionally to "Update from any version"
Using Unbuffered disk I/O = yes?
Disable it or set custom parameter direct_torrent_enabled -> false to keep using unbuffered disk I/O.
Your connection is slower than 1Mbit?
Disable UTP3/ZGT protocol as it may now work well in low-speed environments. Stick to TCP instead.
Using custom parameter choke_peers = true in a Profile?
Set it to false, this parameter is outdated and may prevent Agents from syncing.
Running Linux agents?
Ensure your Linux allows to open at least 8192 file handles, or you may get error Too many open files.
Check core changes.
Verify if any 2.12 related core changes are related to your setup.
Your version is 2.9 or even earlier?
Do a two-step upgrade, upgrade to 2.12 first, then update to latest 3.x. Contact support for assistance
Using API for a long time?
Check if you have outdated API tokens which are not supported by MC 3.6 and newer. Those tokens can be distinguished by its length - they are short (20 bytes). Delete the old token and generate a new one.
Using %FOLDERS_STORAGE% macro in any job?
Ensure it is defined in sync.conf configuration file of all agents that are using it.
Using Console API?
Save your API tokens as after the upgrade they only visible at the moment of creation.
Using Ignore modified files = Yes parameter in Job Profile?
Parameter "Ignore modified files" is deprecated in 3.0. You will need to enable "Skip file errors (transfer jobs)" in Agent profile after the upgrade
Using legacy Selective Sync with .rslx placeholders?
Remove agents with legacy selective sync from the jobs before the upgrade as a part of migration to Transparent Selective Sync.