AlexP11223 / qBTConverter

Tool for replacing paths in qBittorent .fastresume files (for example, when moving to different PC/OS, especially from Windows to Linux/MacOS)
72 stars 3 forks source link

Question on Transferring Windows to Linux (Docker / Unraid) #4

Open jeff15110168 opened 3 years ago

jeff15110168 commented 3 years ago

Does this program also transfer all the history/ratio/active/seeding torrents after following the wiki guide below? I'm basically trying to accomplish the same thing as this person i.e. moving a very large Windows install to Docker and want to make sure i don't mess up the 10tb+ of torrents i'm currently seeding.

Also what is the difference between qBTConverter, qbtchangetracker and QB_Migrate_to_Linux?

1. Re-create all your categories in the Linux qBittorrent client.
2. Shutdown qBittorent on all your machines (both Windows and Linux).
3. Transfer all torrent DATA FILES and KEEP THE SAME FILE STRUCTURE (from windows to linux).
4. Copy all torrent files from C:\Users\<your user>\AppData\Local\qBittorrent\BT_backup to /home/<your linux qbittorrent user>/.local/share/data/qBittorrent/BT_backup.
5. Run this tool as described above and move everything from C:\Users\<your user>\AppData\Local\qBittorrent\BT_backup\out to /home/<your linux qbittorrent user>/.local/share/data/qBittorrent/BT_backup.
AlexP11223 commented 3 years ago

.fastresume files contain the path where the downloaded content is stored, and some other info about the torrent.

These apps can replace the paths, so that you will be able to continue seeding without specifying new content locations manually for each torrent and waiting lots of time while it re-checks all files.

QB_Migrate_to_Linux seems to be doing the same thing as this app, maybe with a bit more guidance/options about how to replace paths.

qbtchangetracker's main purpose seems to be replacing tracker server addresses, but it also has an option for paths, which should do the same thing too.

jeff15110168 commented 3 years ago

.fastresume files contain the path where the downloaded content is stored, and some other info about the torrent.

These apps can replace the paths, so that you will be able to continue seeding without specifying new content locations manually for each torrent and waiting lots of time while it re-checks all files.

QB_Migrate_to_Linux seems to be doing the same thing as this app, maybe with a bit more guidance/options about how to replace paths.

qbtchangetracker's main purpose seems to be replacing tracker server addresses, but it also has an option for paths, which should do the same thing too.

I see, thank you so much for your reply :)

Does the fast-resume / BT_Backup also transfer over the "Statistics" info of qBit? I have like 12+ years of statistics in there so it would be nice to continue to build that if possible, but it's not a dealbreaker at the end of the day.

AlexP11223 commented 3 years ago

It's probably stored in some other file that you can just copy. Maybe qBittorrent-data.conf (in ~/.config/qBittorrent on Linux).

jeff15110168 commented 3 years ago

It's probably stored in some other file that you can just copy. Maybe qBittorrent-data.conf (in ~/.config/qBittorrent on Linux).

that worked! I just renamed the "qBittorrent-data.ini" to "qBittorrent-data.conf" and moved it into /mnt/user/appdata/qbittorrent/qBittorrent/

jeff15110168 commented 3 years ago

@AlexP11223 I ran the program using the command qBTConverter "C:\Users\User\Downloads\BT_backup" "H:\Downloads" "/downloads/" and it replaced all the BT_Backup files (I have ~100 torrents) with the correct names I think. I then closed qBittorrent docker, moved all those corrected files from output folder to docker's BT_Backup folder. When I started the QBT docker it started redownloading all my files again.

How do I prevent this? It just messed up around 7TB of files by forcibly redownloading. Luckily I still have my old hard drives with the completed files so I'm going to have to wipe these disks and re-try this process. What did I do wrong?