search

zadam / trilium

Build your personal knowledge base with Trilium Notes
GNU Affero General Public License v3.0
27.2k stars 1.9k forks source link

(Bug report) Restoring from backup doesn't work #4640

Open axg20202 opened 8 months ago

axg20202 commented 8 months ago

Trilium Version

0.62.6

What operating system are you using?

Windows

What is your setup?

Local (no sync)

Operating System Version

TrueNAS and Windows

Description

I am trying to restore from a backup file. I've followed the Wiki instructions for both my TrueNas app install and desktop install. In both cases, swapping out the document.db file prevents the application from launching.

Strangely, there is no import feature for old Trillium database notes. This would really be an obvious feature to add. At the moment, it seems easier to import notes from other apps than import old Trilium notes that are in Trilium format, which is a problem.

Error logs

No response

Nriver commented 8 months ago

Run from terminal and see the logs.

axg20202 commented 8 months ago

Thanks. It looks as though there is a version mismatch:

"App db version is 227, while db version is 197. Migration needed. ERROR: Direct migration from your current version is not supported. Please upgrade to the latest v0.60.4 first and only then to this version."

How do I know which database version a previous release uses? Or is there a way to migrate an old database file to the latest version?

meichthys commented 8 months ago

I think you will need to update incrementally. You can view the release notes to see which versions required a version change, but generally there are only version changes in the major versions, i.e. going from v0.59 to v0.60 etc.

axg20202 commented 8 months ago

OK, thanks. I had to download every major release and open the db file in each working my up to the current release. There has to be a better way to manage backups than the current implementation.

zadam commented 8 months ago

The fact you had to download an older release to migrate is unfortunate, but it is not a regular occurence, IIRC such cut-off has happened twice in the Trilium release history because of too large migration changes. Trilium is not going to make such big (DB) changes anymore and therefore this shouldn't happen again.