This guide will help you migrate Resilio Agent to the new server preserving its configuration.
Migration of the Agent implies moving its storage folder to the new server. Storage folder is the directory where the Agent keeps its setting, database files, debug logs and other service information. By default, storage is created in the directories mentioned here.
1. To ease the migration, it is highly advisable to migrate the Agent when it's mainly idle, not busy with file transfers.
2. Do not perform upgrade during the migration. Install the same Agent version as was installed on the older server.
3. The migrated Agent may request approval on MC. It's OK, proceed with approval.
4. After the migration is completed, uninstall and do not start the previous Agent installation on the older server.
5. Make sure the agent has access to the files it was syncing before via the same path that is configured in the Job settings.
1. Stop Resilio Connect Agent service.
2. Install Resilio Connect Agent on the new server. Do not launch it.
3. If the Agent's storage was encrypted on the old server (for versions 3.6 and newer), copy the encryption key (environment variable value) to the new server and set it up the same way.
4. Copy the content of its current storage folder to the exact same location on the new server. If you use custom (non default) storage location, please check this guide to adjust the path on the new server accordingly.
5. Start the Resilio Connect Agent service on the new server.
It is expected that the Agent will reconnect to the Management Console and not create a new Agent entity there.
Depending on how you have Resilio Connect Agent installed, use either of the methods
1) This is just downloaded and launched rslagent binary file
- stop rslagent process.
- If the Agent's storage was encrypted on the old server (for versions 3.6 and newer), copy the encryption key (environment variable value) to the new server and set it up the same way.
- copy the content of current storage to the new server
- download the Agent binary and point it to the new storage location. Depending on how it was set up on the older server, two options are possible:
One of the options is to add
--storage /path/to/new/storage parameter to the launch line. The launch line must have also --server parameter to connect to the Management Console.Another option is to add
"storage_path": "/path/to/new/storage", into the configuration file. Configuration file must have Management Server configured as well. Be sure to stick to json format- start the Agent
2) Agent is installed through package manager
- stop the daemon
- If the Agent's storage was encrypted on the old server (for versions 3.6 and newer), copy the encryption key (environment variable value) to the new server and set it up the same way.
- copy content of the current storage folder to the same location on the new server. Check this guide to learn about the default storage location
- If you know you had adjusted the service file in some way so that it's not default one anymore, copy it to the new server as /lib/systemd/system/resilio-agent.service.d
- install the service, do not start it
- run command
sudo systemctl daemon-reload - start the daemon
It is expected that the Agent will reconnect to the Management Console and not create a new Agent entity there. Recheck the jobs and Agent configuration. If everything seems OK, you can clear the storage and Agent installation on the old server.
1. Stop Resilio Connect Agent.
2. If the Agent's storage was encrypted on the old server (for versions 3.6 and newer), copy the encryption key (environment variable value) to the new server and set it up the same way.
3. Copy the content of current storage folder to the exact same location on the new device, including the sync.conf file if it's there.
4. If you used non-default storage location, see this guide to adjust the path to it on the new server accordingly.
5. Download and launch Resilio Connect Agent on the new device.
It is expected that the Agent will reconnect to the Management Console and not create a new Agent entity there.
6. Recheck the jobs and Agent configuration. If everything seems OK, you can clear the storage and Agent installation on the old server.