aboutsummaryrefslogtreecommitdiff
path: root/doc/administration/backup.rst
diff options
context:
space:
mode:
Diffstat (limited to 'doc/administration/backup.rst')
-rw-r--r--doc/administration/backup.rst12
1 files changed, 9 insertions, 3 deletions
diff --git a/doc/administration/backup.rst b/doc/administration/backup.rst
index fb379bc..0643728 100644
--- a/doc/administration/backup.rst
+++ b/doc/administration/backup.rst
@@ -15,13 +15,19 @@ case data is lost due unforseen reasons.
Backup
------
-The Fietsboek data lives in two places: Most of it is saved in the database,
-while track images and other "big files" are saved in the data directory.
+The Fietsboek data lives in two places: Track and account metadata is saved in
+the database, while GPX files, images and other "big files" are saved in the
+data directory.
You should refer to the manual of your DBMS to see what the procedure for a
backup is. Using the preferred way for your DBMS ensures that your backup
represents a consistent state of the database.
+.. note::
+
+ Check :doc:`maintenance-mode` to see how the maintenance mode can be
+ enabled, which should disable most database accesses during the process.
+
After backing up the database, you should back up the data directory with a
tool of your choice, for example by using ``tar``, ``rsync`` or a proper backup
tool like ``borg``:
@@ -82,7 +88,7 @@ specific version:
.. code:: bash
- .venv/bin/pip install "fietsboek==vX.Y.Z"
+ .venv/bin/pip install "fietsboek==X.Y.Z"
Next, we run the data migrations: