How to back up the database for self hosted diary fans

Steps for self-hosted diary fans to back up their diary database, what to prepare first, and mistakes that leave a backup unusable.

By VLClean · 2026-11-01

VLClean is published by the makers of Askarr and Watcharr, which are compared here alongside other tools.

Self-hosted diary fans can back up their database by finding the file or service the diary app writes to, pausing new entries if the app allows it, copying the database to a second location, and opening the copy to confirm it works. Use the app's own export option if it has one. The steps below explain each part.

Option	How it helps with the backup	Cost details
The diary app's own export	Creates an export file from inside the diary app, if the app offers one. Check its documentation for the format.	not published
Copy of the database file with the app stopped	Copies the file the app writes to, with the app paused so the copy is complete.	not published
Scheduled copy with a script	A script you run on a timer copies the file or export to a second location.	not published
Watcharr	Turns a public IMDb list into links for Radarr and Sonarr ^[1]. The sources on this page do not describe any Watcharr backup feature.	not published

What you need before you start

Find out which program holds your diary entries, and where its database file or database service is kept. The program's documentation usually names it.

Have a second place ready to store copies, such as an external drive or another computer on your network. A copy kept on the same disk as the original does not protect you if that disk fails.

Make sure you have admin or command-line access to the server, since reading or copying the database usually needs it. Keep the server and app login details in a safe place, separate from the backups.

Decide how often you will back up, and write the schedule down so it does not depend on memory. Check that the storage has enough free space for a full copy plus the entries you expect to add. Pick a quiet time for the first run, when you are not adding entries.

Step by step

The exact method depends on the diary app, so check its documentation for the file name and any export option.

Find the database file or the database service the diary app uses, and write its location down.
Pause new entries if the app allows it, or run the backup at a quiet time so the copy is not taken mid-write.
Use the app's own export or dump option if it has one. If it does not, copy the database file while the app is stopped.
Name the copy with the date and the app name, so backups are easy to tell apart later.
Move the copy to a second location, not the server's own disk.
Set a regular schedule, and record when it runs.
Open the copy in a test setup or a spare copy of the app to check that the entries appear.
Delete old copies on a schedule you wrote down, keeping enough to go back a few steps.

Tools that can do it

Watcharr turns a public IMDb list into one link for Radarr with the movies and one link for Sonarr with the shows. ^[1] Each link acts like a small Radarr or Sonarr server, so Radarr checks it every 15 minutes and Sonarr every 5. ^[1] The hosted version needs nothing to install and no account. ^[1] The sources on this page do not describe any Watcharr backup feature.

The other options below are methods rather than named tools, since no facts about specific diary or backup tools were supplied for this page. Check whether your diary app has a built-in export option, since that is the simplest copy to make.

Common mistakes to avoid

Avoid keeping the only copy on the same disk as the server, because one disk failure then takes both the database and its backup.

Avoid copying the database while the app is writing to it, which can leave a copy that will not open.

Avoid never testing a restore. A backup you have not opened may not work when you need it.

Avoid letting old copies pile up until the disk fills, since that can stop the next backup from running.

Avoid trusting a schedule you set once and never check. Look at the copies now and then to confirm new files are appearing with a sensible size.

Frequently asked questions

How can self-hosted diary fans back up the database?

Find the database file or the database service the diary app uses, pause new entries if the app allows it, and copy the database to a second location with the date in its name. Use the app's own export option if it has one, since that is often the simplest copy to make. Then open the copy in a test setup to confirm the entries appear. The step-by-step section above lists each action in order.

Does Watcharr back up a diary database?

Watcharr is a tool that turns a public IMDb list into links for Radarr and Sonarr. ^[1] The hosted version needs nothing to install and no account. ^[1] The sources on this page do not describe any Watcharr backup feature. For the diary database itself, use the diary app's own export or a copy of the database file taken while the app is paused.

Where should self-hosted diary fans store database backup copies?

Store copies in a second place, such as an external drive or another computer on your network, so a failure on the server's own disk does not take the copies with it. Give each file a dated name, and delete old copies on a schedule you wrote down, keeping enough to go back a few steps. A copy in the same spot as the original is a weaker backup, and a copy you never open may not work when you need it.

How often should self-hosted diary fans back up the database?

Pick a schedule that matches how often you add entries, and write it down so it does not depend on memory. The right interval depends on how much you could afford to lose, so decide that first. After each run, check that a new file appeared with a sensible size. Set a reminder to test a restore now and then, so you know the copies open.

Can a diary database be copied while the app is running?

Copying while the app is writing can produce a copy that will not open, so pause new entries first if the app allows it, or stop the app for the copy. Use the app's own export option when it has one, because that does not depend on copying a file that is in use. Check the diary app's documentation for the method it recommends, and test the copy by opening it before you rely on it.

Its code is available to read under the PolyForm Noncommercial 1.0.0 licence; older versions remain under MIT. ^[1]

Try Watcharr

Sources

Watcharr's own description of itself (the product of this site's publisher)