Short answer: Yes — you can migrate 100+ torrents from rTorrent 15 to rTorrent 16, but you must do it carefully so torrents re-check against existing data and so any rTorrent-Pro post-processing (AutoMove / Media Library) works. The safest approaches are (A) re-add existing .torrent files so rTorrent re-checks the data, then handle AutoMove manually; or (B) preserve/restore rTorrent session/config so jobs are kept across the upgrade. Below are practical, proven procedures, warnings and workarounds (including how to trigger AutoMove / Finished behavior).
Important safety notes (read first)
What the forum fragments say (authoritative for behavior)
Two reliable migration methods (pick one depending on what you can/do want to preserve)
Method A — Re-add torrents (recommended when you have .torrent files or can export them)
Use this when you can export/download the .torrent files for each job (or copy them from rTorrent’s watch/backup). This is usually the simplest and safest.
1) Backup:
2) Collect torrent files:
- Get the .torrent files for all jobs. If rTorrent stored them (watch directory), copy those .torrent files out. If you only have magnet links, export them into .torrent (tracker clients or websites can help) — but magnets require re-download of metadata.
3) Place data in expected download paths:
- For each torrent, ensure the data files are located at the path rTorrent will expect for re-check. If your rTorrent config uses separate download/complete folders, move or copy the data into the configured download path (or create hardlinks into that path). Hardlinks are ideal because they avoid re-copying large files.
4) Re-add torrents:
5) Trigger post-processing / AutoMove (workarounds):
6) Verify:
Method B — Preserve/restore rTorrent session (recommended if you want to keep job states, labels and don't want to re-add)
Use this when you want to preserve the jobs as they appear in rTorrent (same hashes, progress, labels, queue positions).
1) Backup everything, including rTorrent’s session directory and config.
2) Stop rTorrent/rTorrent-Pro.
3) Copy the session directory and config from the rTorrent 15 installation to the same expected locations for rTorrent 16. Keep ownership and permissions identical.
4) Start rTorrent 16 and inspect the job list. Many times jobs reappear unchanged and rTorrent will continue seeding. If rTorrent 16 has changed session file format, consult release notes; sometimes an in-place migration is supported but must be done by the app during first start.
5) If jobs are present but paths differ or rTorrent marks data missing, move data or update paths (see step 3 in Method A) then instruct rTorrent to re-check.
Handling AutoMove / Finished-event problem (detailed)
- Use rTorrent-Pro Advanced UI “Move” or “Archive” function after re-check to manually run the same post-processing the Finished event would have triggered.
- Scripted approach: If you are competent, write a small script that uses rTorrent’s XML-RPC interface to call the same functions AutoMove would use (this requires familiarity with XML-RPC and rTorrent commands). Test on 1–2 torrents first.
- If you must trigger Finished events, another trick is to temporarily change the torrent’s state so rTorrent thinks it has pending pieces and then let it re-verify/complete; this is fiddly and error-prone — avoid unless you know what you’re doing.
Other practical tips, drawn from forum behaviors
Quick checklist to run now (summary you can follow)
1) Stop rTorrent/rTorrent-Pro in App Center.
2) Backup rTorrent session, config, and all downloaded data.
3) Decide method: re-add .torrent files (A) or copy session files (B).
4) If A: collect .torrent files, place data in rTorrent’s download path (use hardlinks if large), drop .torrent files into watch dir, start rTorrent, let it re-check.
5) If B: copy session/config into new install locations, start rTorrent and verify jobs appear. Fix any path mismatches and re-check as needed.
6) For AutoMove/MediaLibrary: either create hardlinks to completed folder, use rTorrent-Pro Advanced UI Move/Archive, or run a tested XML-RPC script to trigger post-processing — avoid ad-hoc file moves that rTorrent does not know about.
7) Verify trackers, seeding, and that media services see content. Keep the original backups until you are 100% sure everything works.
If you want one compact recommended route for 100+ torrents: stop rTorrent, backup session/config and data, collect all .torrent files, place data into the configured download path using hardlinks (to avoid copying), restart rTorrent and re-add the .torrent files to the watch folder so rTorrent re-checks; then use hardlinks or Advanced UI Move to populate your completed/MediaLibrary locations so downstream services see content (because re-check does not fire Finished/AutoMove automatically).
Final reminder: Back up before touching session files or moving data. Test on a small set of torrents first.
Źródła na forum:
Important safety notes (read first)
- Always make a full backup of user data and of rTorrent’s config/session files before starting. Any operation touching torrents, session files, or moving/deleting data can break seeding and cause data loss.
- If your NAS uses a separate download/complete/media layout or rTorrent-Pro hardlinks, preserve that layout and test the procedure on a few torrents first.
- The forum fragments show that re-checked torrents may NOT emit the “Finished” event that AutoMove watches for — plan for that.
What the forum fragments say (authoritative for behavior)
- Re-adding a .torrent that already has files in place causes rTorrent to re-check and go straight to Seeding, but typically does not trigger the Finished event — therefore AutoMove does not run automatically. (fragment [1])
- rTorrent-Pro supports hardlinks and its post-processing (AutoMove) works differently when a torrent truly completes vs when it is imported as already-present files; hardlinks can be used to move or archive without breaking seeding. (fragments [3], [6])
- rTorrent uses Download share by default on QNAP and can be redirected by creating a special Rdownload share and restarting the app. Stop rTorrent-Pro before creating such share. (fragment [4])
Two reliable migration methods (pick one depending on what you can/do want to preserve)
Method A — Re-add torrents (recommended when you have .torrent files or can export them)
Use this when you can export/download the .torrent files for each job (or copy them from rTorrent’s watch/backup). This is usually the simplest and safest.
1) Backup:
- Stop rTorrent/rTorrent-Pro service in App Center.
- Copy rTorrent config and session files (wherever your installation stores them) to a safe location.
- Ensure you have a safe copy of all downloaded data (or at least a filesystem snapshot / backup).
2) Collect torrent files:
- Get the .torrent files for all jobs. If rTorrent stored them (watch directory), copy those .torrent files out. If you only have magnet links, export them into .torrent (tracker clients or websites can help) — but magnets require re-download of metadata.
3) Place data in expected download paths:
- For each torrent, ensure the data files are located at the path rTorrent will expect for re-check. If your rTorrent config uses separate download/complete folders, move or copy the data into the configured download path (or create hardlinks into that path). Hardlinks are ideal because they avoid re-copying large files.
4) Re-add torrents:
- Put each .torrent into rTorrent’s watch directory (or use the GUI to add the torrent, selecting the correct download directory).
- rTorrent will re-check the files and, if everything matches, change state to Seeding. It will NOT normally emit a Finished event after a re-check, so AutoMove will not run automatically (this is the fragment [1] behavior).
5) Trigger post-processing / AutoMove (workarounds):
- Option 1 (recommended for rTorrent-Pro): Use hardlinks — create hardlinks from the download location to your completed/MediaLibrary path. Because the files are present in the completed path, downstream services (Plex/MediaLibrary) will see them. You can then use rTorrent-Pro Advanced UI “Move” operation to tell rTorrent where the new completed path is (if supported), or leave as-is and treat completed as an archive.
- Option 2 (manual trigger): Use an XML-RPC command or rTorrent control utility to programmatically call the finished handler for each torrent. If you are not confident with XML-RPC/scgi calls, avoid this — it's advanced and can misbehave if done wrong.
- Option 3 (safe UI method): For a small batch, let one torrent actually finish naturally (e.g., create a low-size test torrent) to observe how AutoMove behaves, and then for imported ones use the GUI to Move/Relocate/Archive the job (rTorrent-Pro Advanced UI provides move/organize operations).
6) Verify:
- Confirm torrents are seeding and trackers show them as active.
- Confirm MediaLibrary / Plex / AutoMove destinations have the expected data (if you used hardlinks, ensure those files are accessible to those services).
Method B — Preserve/restore rTorrent session (recommended if you want to keep job states, labels and don't want to re-add)
Use this when you want to preserve the jobs as they appear in rTorrent (same hashes, progress, labels, queue positions).
1) Backup everything, including rTorrent’s session directory and config.
2) Stop rTorrent/rTorrent-Pro.
3) Copy the session directory and config from the rTorrent 15 installation to the same expected locations for rTorrent 16. Keep ownership and permissions identical.
4) Start rTorrent 16 and inspect the job list. Many times jobs reappear unchanged and rTorrent will continue seeding. If rTorrent 16 has changed session file format, consult release notes; sometimes an in-place migration is supported but must be done by the app during first start.
5) If jobs are present but paths differ or rTorrent marks data missing, move data or update paths (see step 3 in Method A) then instruct rTorrent to re-check.
Handling AutoMove / Finished-event problem (detailed)
- Why it fails: When you re-add an existing data set, rTorrent marks it seeding directly and does not emit the Finished event that AutoMove listens for (fragment [1]).
- Practical fixes:
- Use rTorrent-Pro Advanced UI “Move” or “Archive” function after re-check to manually run the same post-processing the Finished event would have triggered.
- Scripted approach: If you are competent, write a small script that uses rTorrent’s XML-RPC interface to call the same functions AutoMove would use (this requires familiarity with XML-RPC and rTorrent commands). Test on 1–2 torrents first.
- If you must trigger Finished events, another trick is to temporarily change the torrent’s state so rTorrent thinks it has pending pieces and then let it re-verify/complete; this is fiddly and error-prone — avoid unless you know what you’re doing.
Other practical tips, drawn from forum behaviors
- Test on a subset first (10 torrents). Confirm re-check, seeding, and MediaLibrary behavior.
- If you use QNAP shares (Download vs Rdownload), stop the app before creating/moving shares; create the Rdownload share if you want a different base path (fragment [4]).
- When moving files between download/complete/MediaLibrary, prefer hardlinks to avoid breaking seeding history. The forum notes Advanced UI remove behavior when hardlinks are used — deleting in the UI deletes the original, but hardlinked archive remains (fragment [3]).
- If you rely on labels/destination sorting created by placing torrents into different watch subfolders, recreate that structure in the new rTorrent watch directories if needed (fragment [2], [3]).
Quick checklist to run now (summary you can follow)
1) Stop rTorrent/rTorrent-Pro in App Center.
2) Backup rTorrent session, config, and all downloaded data.
3) Decide method: re-add .torrent files (A) or copy session files (B).
4) If A: collect .torrent files, place data in rTorrent’s download path (use hardlinks if large), drop .torrent files into watch dir, start rTorrent, let it re-check.
5) If B: copy session/config into new install locations, start rTorrent and verify jobs appear. Fix any path mismatches and re-check as needed.
6) For AutoMove/MediaLibrary: either create hardlinks to completed folder, use rTorrent-Pro Advanced UI Move/Archive, or run a tested XML-RPC script to trigger post-processing — avoid ad-hoc file moves that rTorrent does not know about.
7) Verify trackers, seeding, and that media services see content. Keep the original backups until you are 100% sure everything works.
If you want one compact recommended route for 100+ torrents: stop rTorrent, backup session/config and data, collect all .torrent files, place data into the configured download path using hardlinks (to avoid copying), restart rTorrent and re-add the .torrent files to the watch folder so rTorrent re-checks; then use hardlinks or Advanced UI Move to populate your completed/MediaLibrary locations so downstream services see content (because re-check does not fire Finished/AutoMove automatically).
Final reminder: Back up before touching session files or moving data. Test on a small set of torrents first.
Źródła na forum:
- Migrating from Download Station: Triggering AutoMove?
- 15.7-777 - first steps - how to pick folder per each torrent?
- The difference between torrenting on a PC and NAS - Common issues, Best Practices
- How-To change downloaded data path to another disk volume
- rtorrent zmiana katalogów
- rTorrent - Przenoszenie torrentów w inne miejsce
Ta wiadomość pochodzi od asystenta AI — może zawierać błędy, zweryfikuj przed zastosowaniem. Oceń ją, głosując pod postem: ▲ pomocna lub ▼ nieprzydatna.
Na tym forum nie ma złych ocen — wszyscy wciąż się uczymy i wszyscy jesteśmy adminami, a +1 czy −1 to zawsze tylko 1 punkt. Każde Twoje kolejne pytanie to wspólna pomoc, która zostaje nie tylko na forum, ale i w internecie. Społeczność forum QNAP działa od 2008 roku i po niemal dwóch dekadach nieprzerwanie dostarcza rzetelne treści, z których korzystają kolejni admini — a ostatnio uczy się na nich także AI.
- 5 Kwiecień 2008
- 10 228
- 2 509
- 405
- Odznaki
- 205
- QNAP
- TS-x77
- Ethernet
- 1 GbE
Poz.
6
Just find out default session folder location is not /share/CACHEDEV1_DATA/Download/rtorrent16/session but /share/CACHEDEV1_DATA/.qpkg/rtorrent16/var/session
Thanks everything works now.
Thanks everything works now.
- 5 Kwiecień 2008
- 10 228
- 2 509
- 405
- Odznaki
- 205
- QNAP
- TS-x77
- Ethernet
- 1 GbE
Poz.
6
Yes.
You can basically change it and even use backups and restore session anytime.
This is designed to let user use for example NVMe drives used for their system to hold sessions. So they can keep sessions together with installation directory.
However when they found this and play a little bit with the settings, they can figure out instead of keeping sessions together with the app, they can simply create in a QNAP new share for Rtorrent operational files on the NVMe drives itself. Eg.:
HDD's for users data
+ Rtorrent downloads
NVMe for their system
+ new share for Rtorrent sessions
This scenario gives you maximum performance.
Podobne tematy
- Pytanie
