From df26c4636abe9d03fb915ae93f13b40de1f1065a Mon Sep 17 00:00:00 2001
From: Adar Nimrod <nimrod@shore.co.il>
Date: Sat, 26 Apr 2025 21:18:08 +0300
Subject: [PATCH] docs: Document the backup and restore procedures.

---
 backup/README.md | 14 ++++++++++++++
 1 file changed, 14 insertions(+)
 create mode 100644 backup/README.md

diff --git a/backup/README.md b/backup/README.md
new file mode 100644
index 0000000..5759ba9
--- /dev/null
+++ b/backup/README.md
@@ -0,0 +1,14 @@
+# Backup and restore
+
+## Backup
+
+Backups are done on the host01 machine and are scheduled via GitLab CI/CD.
+They're stored under `/var/backups/registry`.
+
+## Restore
+
+Because uploads are only allowed from the machine that hosts the registry
+(ns4), the restore also needs to done there. So first step is copying the
+backup directory to ns4 (`scp -r host01.shore.co.il:/var/backups/registry ns4.shore.co.il:/home/nimrod/` should do the trick). Afterwards build the image
+on the host (`docker --context ns4 build -t reg-backup .`) and run the restore
+script with the directory mounted as a volume (`docker --context ns4 run --rm -v /home/nimrod/registry/:/registry:ro reg-backup restore /registry registry.shore.co.il`).
-- 
GitLab