Question re: Backup-Strategy

Operating system

Linux

Joplin version

3.7.21

What issue do you have?

Dear all,
I noticed that .config/joplin-desktop is taking up a lot of space in my regular backups; is there any benefit in backing up .config/joplin-desktop as part of my home directory when I am already using the built-in backup plugin of Joplin?

Built-in backup is mostly enough but if you have a space I'd backup both, simply because it's easier to restore from the profile if you lose your laptop or it breaks down. You could exclude the .crypted files if that helps

Would that be valid & helpful even if my (separate) folder with the 10 Joplin plugin Backups is also backed up regularly because it is in my Home directory?

Hi,

I would say just go ahead and back it up. It's good to have.

Yes, ~/.config/joplin-desktop/ is the standard Joplin Desktop profile directory on Linux.

It contains both:

  • Configuration: Application settings, plugins, keyboard shortcuts, and preferences.

  • Local data replica: The SQLite database (database.sqlite) containing your notes, notebooks, tags, and synchronization information, plus the resources/ directory containing attachments such as images and PDFs.

If you back up this entire directory while Joplin is closed, you preserve both your configuration and your local Joplin data.

You can also copy this directory to another Linux computer to migrate your Joplin profile, preferably with the same Joplin version installed.

One caveat: Flatpak installations typically use a different profile location.

Thanks. It's just not clear to me if I am not saving the same data twice, since everything would be in the regular Joplin Backup plugin job as well as in my hourly rsync backup of the home directory

So if my current laptop were to break down, I would have to choose between using one of the Joplin backups created by the plugin or the .config/joplin-desktop/ data from my rsync backup. But since space is not an issue I'll just stick to both and hope I will never need them.

Hi,

I don't know anything about the backup plugin that you're planning to use.

Say, for example, Joplin is using 500 MB or maybe as much as 1 GB and that data is stored both on your synchronization server and on each client that synchronizes with the server.

Without backups you would need to install a clean version of Joplin, set up the synchronization, and synchronize all of your data down to that client again. For me this is not a big deal because I don't have a ton of data. If you have many gigabytes of data, then getting back up and running via synchronization could take longer.

Backing up the profile directory makes that backup portable. What this means is that you can restore that backup to another computer and you'll have Joplin up and running in a matter of minutes on another computer.

If your laptop goes kaput all you need to do is install Joplin and then restore your profile directory and you're done. Joplin is all configured just as it was before the crash.

As you mentioned it's probably a minimal amount of data and it won't affect the amount of storage that your backups consume.

Also take a look at a backup program called Kopia. You might find it more useful than rsync. It's open source, free, and runs on Windows, Linux, and Mac. It's what I use to back up all my data and configuration files. I have, in the past decades, tried to learn how to use rsync but never mastered it.

It does automatic deduplication so none of your data gets backed up twice.

One more important thing I forgot to mention.

It is very important to first exit from Joplin before backing up the profile directory. All of the files need to be closed. The database needs to be closed so that you can back up all of the files rather than skipping the ones that are open (which is the database).

FWIW the Joplin flatpak uses the same location as every other package. I think the only package that does differ is the snap - which also moves the backup plugin folder by default too (to ~/snap/joplin-desktop/common)