From b60ea748453f21a2062ad6be7c20bb148107762a Mon Sep 17 00:00:00 2001 From: Rafael Kraut Date: Wed, 23 Mar 2022 18:27:40 +0100 Subject: [PATCH] Fix link to point to new docs location (#382) --- docs/backup_restore/b_n_r-backup.en.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/backup_restore/b_n_r-backup.en.md b/docs/backup_restore/b_n_r-backup.en.md index 99d2e91e3..50d29f0ce 100644 --- a/docs/backup_restore/b_n_r-backup.en.md +++ b/docs/backup_restore/b_n_r-backup.en.md @@ -49,7 +49,7 @@ This following script may be placed in `/etc/cron.daily/mailcow-backup` - do not #!/bin/sh # Backup mailcow data -# https://mailcow.github.io/mailcow-dockerized-docs/b_n_r_backup/ +# https://mailcow.github.io/mailcow-dockerized-docs/backup_restore/b_n_r-backup/ set -e @@ -94,4 +94,4 @@ Do **not** rsync to a Samba share, you need to keep the correct permissions! To restore you'd simply need to run rsync the other way round and restart Docker to re-read the volumes. Run `docker-compose pull` and `docker-compose up -d`. If you are lucky Redis and MariaDB can automatically fix the inconsistent databases (if they _are_ inconsistent). -In case of a corrupted database you'd need to use the helper script to restore the inconsistent elements. If a restore fails, try to extract the backups and copy the files back manually. Keep the file permissions! \ No newline at end of file +In case of a corrupted database you'd need to use the helper script to restore the inconsistent elements. If a restore fails, try to extract the backups and copy the files back manually. Keep the file permissions!