Move borg dump staging to backup share

2026-04-15 09:37:49 +02:00
parent d888d7394b
commit 8b8e96e32f
6 changed files with 336 additions and 4 deletions
@@ -10,7 +10,7 @@ These scripts are intended to run on the Unraid host before a Borg backup starts

 Fresh dump artifacts are written to:

- `/mnt/user/appdata/borg-ui/dumps/latest`
+- `/mnt/user/backups/borg/dumps/latest`

 Borg UI should include `/local/borg-dumps` as a backup source.

@@ -19,3 +19,21 @@ Borg UI should include `/local/borg-dumps` as a backup source.
 - The script is written for host execution where `docker` is available.
 - It does not assume Backrest.
 - It keeps only the latest dump set because Borg itself provides history.
+
+## Recommended automation path
+
+The recommended automation path is:
+
+1. Unraid User Scripts on the host
+2. host-side schedule / cron
+3. Borg UI backup job afterwards
+
+This is preferred over a Borg UI inline hook because the dump script expects:
+
+- host access to `docker exec`
+- host paths like `/mnt/user/...`
+- direct write access to the dump target directory
+
+Do not treat `pre-backup-dumps.sh` as a Borg UI inline script unless the architecture is deliberately changed later.
+
+See `USER_SCRIPTS_SETUP.md` for the intended host-side rollout.