Torrent Migration
In this guide, we will cover the procedure of migrating torrent sessions from one client to another. There are multiple ways of getting this done, and we will show you a few of them. Before we begin with the instructions, we will list all torrent clients available on Ultra.cc, and their respective strengths and limitations.
- Deluge - Unstable and fast downloading, with a limit of 1000 torrents
- qBittorrent - Stable and fast seeding, with a limit of 10K torrents
- rTorrent - Unstable and slow seeding, with a limit of 2000 torrents
- Transmission - Slow and featureless, with a limit of 25K torrents
As these torrent clients are running in a shared environment on Ultra.cc. We do not recommend and neither do we officially support torrent clients with torrent sessions above these limitations.
Instructions
As mentioned previously, there are multiple ways of migrating your torrent session between clients. Below, we will show you a generic way of doing it.
- Connect to your Ultra.cc service via SSH
- Once connected you can find your torrent session stored in these locations:
-
Deluge:
~/.config/deluge/state -
qBittorrent:
~/.local/share/qBittorrent/BT_backup -
rTorrent:
~/.config/rtorrent/session -
Transmission:
~/.config/transmission-daemon/torrents
-
Deluge:
Next, you would want to copy your torrent files from the torrent session directory of your torrent client into the watch directory of the torrent client you would want to migrate to.
- The watch directory is located at
~/watch/<name-of-torrent-client> - If you are migrating to Deluge, it would be
~/watch/deluge - To avoid heavy resource usage that could lead to your torrent client crashing, do not add more than ~50 torrent files at the same time. Once those torrents you have added has been hashed, you can add a new set of 50 torrents.