mirror of
https://github.com/zadam/trilium.git
synced 2025-06-06 18:08:33 +02:00
Updated Backup (markdown)
parent
790a5db8c1
commit
b08c7a65b9
@ -19,7 +19,8 @@ Let's assume you want to restore the weekly backup, here's how to do it:
|
|||||||
* I'll refer to `~/trilium-data` as data directory from now on
|
* I'll refer to `~/trilium-data` as data directory from now on
|
||||||
* find `~/trilium-data/backup/backup-weekly.db` - this is the [[document]] backup
|
* find `~/trilium-data/backup/backup-weekly.db` - this is the [[document]] backup
|
||||||
* at this point stop/kill Trilium
|
* at this point stop/kill Trilium
|
||||||
* copy and rename this `~/trilium-data/backup/backup-weekly.db` to `~/trilium-data/document.db` - this will delete the current state of the [[document]] so you might want to back it up somewhere else
|
* delete `~/trilium-data/document.db`, `~/trilium-data/document.db-wal` and `~/trilium-data/document.db-shm` (latter two files are auto generated)
|
||||||
|
* copy and rename this `~/trilium-data/backup/backup-weekly.db` to `~/trilium-data/document.db`
|
||||||
* start Trilium again
|
* start Trilium again
|
||||||
|
|
||||||
If you have configured sync then you need to do it across all members of the sync cluster, otherwise older version (restored backup) of the document will be detected and synced to the newer version.
|
If you have configured sync then you need to do it across all members of the sync cluster, otherwise older version (restored backup) of the document will be detected and synced to the newer version.
|
||||||
|
Loading…
x
Reference in New Issue
Block a user