summaryrefslogtreecommitdiff
path: root/topics/systems/backups-with-borg.gmi
diff options
context:
space:
mode:
Diffstat (limited to 'topics/systems/backups-with-borg.gmi')
-rw-r--r--topics/systems/backups-with-borg.gmi16
1 files changed, 16 insertions, 0 deletions
diff --git a/topics/systems/backups-with-borg.gmi b/topics/systems/backups-with-borg.gmi
index 5cdb2a3..d5bfd1b 100644
--- a/topics/systems/backups-with-borg.gmi
+++ b/topics/systems/backups-with-borg.gmi
@@ -200,3 +200,19 @@ Our production server runs databases and file stores that need to be backed up t
Once backups work it is useful to copy them to a remote server, so when the machine stops functioning we have another chance at recovery. See
=> ./backup-drops.gmi
+
+# Recovery
+
+With tux04 we ran into a problem where all disks were getting corrupted(!) Probably due to the RAID controller, but we still need to figure that one out.
+
+Anyway, we have to assume the DB is corrupt. Files are corrupt AND the backups are corrupt. Borg backup has checksums which you can
+
+```
+borg check repo
+```
+
+it has a --repair switch which we needed to remove some faults in the backup itself:
+
+```
+borg check --repair repo
+```