How to upgrade daemon w/o rechecking all seeded torrents ?

[tman]

Hi,

I'm using transmission daemon on a Fonera 2.0N device. The dafault daemon that came preinstalled with the device is 1.72. I have downloaded with 1.72 about 1TB of data, about 200 torrents and I'm seeding them.
Now I want to upgrade daemon to 1.90 but I found out that if I install and start the new daemon all my seeded torrents dissapears because the 3 files that are my transmisson installation ( torrent.mfg, torrent.var, torrent.swp) ar overwritten and it looks like a fresh installation.
I tried to add again the torrents and it started re-checking the data, but it can take 2...3 weeks to complete (the device has only a 300mhz processor a 32MB ram)
Questions:
1. Can I upgrade from 1.72 to 1.90 without rechecking the data ?
2. Which file stores what kind of information (var , mfg, swp) ?
3. Can I replace only one of the files to upgrade the daemon and keep the data stored as it is ? If not:
4. Can I extract/convert the information stored in the old installation and import to the new installation ? If not:
5. Can I start seeding without rechecking all data (assuming by default that all data files are completed) ?

Thanks in advance
tman

[tman]

nobody any ideeas? pls. dev guys at least say is possible or not.

[tman]

nobody any ideeas? pls. dev guys at least say is possible or not.

[spanish_biker79]

I had exactly the same question now. I did one upgrade a few weeks ago and all my torrents needed to be rechecked, taking forever...

Not sure about it, but I found a folder called "resume" that seems to store the information for each torrent and another called "torrents" with each torrent.

I was assuming that maybe just backing up these folders could make the trick. If someone could confirm? (or give another alternative)

I'll try to play around a little before doing it though...

[Longinus00]

You should probably talk to the people that package transmission for your devices. They are the ones who decide what gets deleted or moved around when you upgrade.

[spanish_biker79]

Thanks, asking in their forum. Will let you know if I get an answer...

[someguy235]

This is important to me as well. If there isn't already a way to do this, there needs to be. I'm currently seeding 13TB of data with Transmission 1.76. I would like to upgrade to a newer version, but it takes weeks to verify all that data. Can the 'resume' folder be migrated in the way that spanish_biker79 suggests? I'm compiling from source on a RHEL5 server, so I've got some control over what gets deleted when I install.

[Longinus00]

If you're compiling from source nothing has moved since 1.76.

[spanish_biker79]

Yeah, I've tried with 1.84 and a few 1.91 and all good, no need to recheck anything.

I had a problem because they compiled and specific version for a linux enclosure and the problem there was that after rebooting the system the whole .config folder got deleted, that's why you had to redownload all torrent files and recheck, but nothing wrong with Transmission itself.

Anyway, if you're messing around or you've got a lot of seeding data, it'd be good to make a copy of that whole .config folder in case something happens. It'd be a matter of just reusing those settings and torrents to resume in the future...

[tman]

spanish_biker79: where is the .config folder on the fonera F2N file system ? It's not in /tmp/images/torrent , neither in /tmp/mounts/Disc-A1/FoneraApps.

[tman]

Anybody some idea where is the .config folder that should be saved before the upgrade? Developer guys ?
This upgrade issue is annoying, specially when new versions are coming faster then I can recheck my TB of data

Thanks!

[Rolcol]

By default, the settings are saved in ~/.config/transmission/. That's how it's specified in the source code. If you downloaded a package made by people other than the Transmission developers (all of the *nix ones), they may have placed it in a different location.

The source that tells Transmission where to look for the config directory is libtransmission/platform.c(421)

[tman]

Thanks for replying. But I still can't find config/transmission neither simply transmission folder or file on my device. Can you give me an example of filename that i could find with command 'find -name filename' ? A filename that is mandatory for transmission, even if my device runs a low profile version. thank you!

[Rolcol]

Thanks for replying. But I still can't find config/transmission neither simply transmission folder or file on my device. Can you give me an example of filename that i could find with command 'find -name filename' ? A filename that is mandatory for transmission, even if my device runs a low profile version. thank you!

Try settings.json. Even that can be changed, though. If you have any torrents running, you can look for *.resume files.

[tman]

Thanks Rolcol ! I found that file and the rest of the configuration that has to be saved for the upgrade. It worked fine, I had upgraded from 2.04 to 2.11 keeping the running torrents.

+++++++++++++++++++++++++++++++++++++++++++
For anybody looking for a similar solution, here is how should be done (I done it on Fonera 2.0N device, in your case this may vary):
- running 2.04 with torrents at seed
- stop seeding the torrents ! (don't stop the daemon, just pause the torrents)
- make a backup of "resume" and "torrents" folders content (on fonera 2.0n are here: /tmp/images/torrent/var/resume and /tmp/images/torrent/var/torrents)
- stop the transmission daemon - in other words "shut down"
- uninstall the 2.04 version
- install 2.11
- start the 2.11 version
- copy from the backup the content of "resume" and "torrents" folder
- shutdown 2.11 immediately after the restore is done from the backup !
- wait a couple of minutes !
- check if "resume" and "torrents" folders are "gone" (deleted automatically)
- reboot your device ! (very important in case of Fonera 2.0N, otherwise it will not work)
- Transmission daemon 2.11 will start automatically and you will see the same torrents content in the WebUI
- Start the torrents
++++++++++++++++++++++++++++++++++++++++

Many thanks again for people helping in this issue !
tman