Updating sync version from old Trilium

[Dmitrykrz]

The doc says "Versions up to and including v0.90.4 are compatible with the latest zadam/trilium version of v0.63.7. Any later versions of TriliumNext have their sync versions incremented."
How do I do that?
I have good old trilium installed on my windows pc and on remote ubuntu machine as docker. Ubuntu machine works as a server ro host a web interface. Both are synchronized.
The version of both is:

How do I update both? I already tried it, but it says that sync version is wrong, TriliumNext cannot take old database.

[dosubot[bot]]

Hi @Dmitrykrz! I'm Dosu and I’m helping the Trilium team.

To update both your Windows and Ubuntu (Docker) Trilium installations and resolve the sync version error, you need to upgrade both to the same new version, but due to sync version incompatibility, you must also re-initialize sync using the same database on both sides. Here’s how you can do it safely:

1. Pick the most up-to-date Trilium instance (either your Windows PC or Ubuntu server).
2. Back up its database (the document.db file or the entire trilium-data directory). Trilium also creates a backup-before-migration.db automatically before migration, so you can roll back if needed docs.
3. Upgrade both installations to the same desired version (for Docker, pull the new image and restart; for Windows, replace the app files with the new version).
4. On the second machine, delete its existing data directory and replace it with the backup from step 2, so both sides have the same database and document ID discussion.
5. Start Trilium on both machines and set up sync again.

This process ensures both instances use the same sync version and document ID, allowing synchronization to work after the upgrade. There are no official automated migration scripts for crossing the sync version boundary—manual re-initialization is required docs.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[Dmitrykrz]

@dosu dear bot,
why do I need to delete and restore the document.db as you say here "On the second machine, delete its existing data directory and replace it with the backup from step 2, so both sides have the same database and document ID".
If right now they already have identical document.db?

[dosubot[bot]]

If both of your Trilium installations are fully synced and have identical document.db files, you do not need to delete and restore the database on the second machine. You can upgrade both independently using the same new TriliumNext version—this will result in identical upgraded databases, and sync will work as expected. The advice to re-copy the database is just a precaution for cases where the databases might have diverged due to unsynced changes or edits. As long as you ensure both are fully synced and shut down before upgrading, you’re good to go. Just make backups first, as always!
Reference

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[rom1dep]

@Dmitrykrz : @dosu is a chat bot, FYI, and its answers may be misleading at times.

Regarding your original question, trilium will take care of the migrations for you. All you need to do is:

• take down the container
• take a backup of it (even though one is created automatically, this is just good practice)
• pull this image (using the "latest" tag) in place of your current one
• start the updated container, it will run the migrations that happened since 0.62.3 automatically for you, and you should find yourself on top of a server-instance running 0.97.1.
• update the client from there: https://github.com/TriliumNext/Trilium/releases/tag/v0.97.1

[Dmitrykrz]

@Dmitrykrz : @dosu is a chat bot, FYI, and its answers may be misleading at times.

Regarding your original question, trilium will take care of the migrations for you. All you need to do is:

• take down the container
• take a backup of it (even though one is created automatically, this is just good practice)
• pull this image (using the "latest" tag) in place of your current one
• start the updated container, it will run the migrations that happened since 0.62.3 automatically for you, and you should find yourself on top of a server-instance running 0.97.1.
• update the client from there: https://github.com/TriliumNext/Trilium/releases/tag/v0.97.1

Thank you ! It worked

[dosubot[bot]]

You're welcome! Glad to hear the upgrade and migration worked out. If you run into any other issues or have questions about Trilium, just let me know!

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[eliandoran]

@Dmitrykrz , I recommend you also try the "TriliumNext" theme in Settings -> Appearance, you might like it. :)