From 6105e9754a92fbf0cfde2fa7c6425d4e8a57bfa1 Mon Sep 17 00:00:00 2001 From: CasVT Date: Mon, 3 Jul 2023 17:01:15 +0200 Subject: [PATCH] Added backup and recovery docs --- docs/backup_your_data.md | 23 +++++++++++++++++++++++ project_management/mkdocs.yml | 1 + 2 files changed, 24 insertions(+) create mode 100644 docs/backup_your_data.md diff --git a/docs/backup_your_data.md b/docs/backup_your_data.md new file mode 100644 index 0000000..4d14dd9 --- /dev/null +++ b/docs/backup_your_data.md @@ -0,0 +1,23 @@ +# Backup your data + +It's possible, and very easy, to backup all MIND data. This way, you can recover data if something goes wrong, port your instance over to an other computer or run redundant instances. + +## Backing up the data + +It's as simple as making a copy of the database file and storing it somewhere safe. + +1. Stop MIND, if it's still running. +2. Go inside the docker volume of the container (most likely `mind-db`) or the mapped folder. +3. Inside the volume/folder, you'll find the `MIND.db` file. Make a copy of this. That's all you need. +4. You can now start the instance back up. + +The database file contains all data and is the only thing needed to keep a complete backup of your MIND instance. + +## Recovering the data + +It's as simple as putting the database file in the database folder and restarting the instance. + +1. Stop MIND, if it's still running. +2. Go inside the docker volume of the container (most likely `mind-db`) or the mapped folder. +3. Inside the volume/folder, place the database file that you backed up. +4. You can now start the instance back up. Everything should be recovered. diff --git a/project_management/mkdocs.yml b/project_management/mkdocs.yml index 6c5b31f..be312fd 100644 --- a/project_management/mkdocs.yml +++ b/project_management/mkdocs.yml @@ -82,3 +82,4 @@ nav: - Setup After Installation: setup_after_installation.md - Other Docs: - API: api.md + - Backup Your Data: backup_your_data.md