fix: point dump_db.sh at its /opt/backup-agent deploy path, remove healthcheck

dump_db.sh no longer lives under $TARGET, so its own default dump
directory (relative to wherever the script is) would land outside the
backed-up tree. Pin DUMP_SCRIPT to /opt/backup-agent/dump_db.sh and
export DUMP_DIR explicitly so dumps still land in $TARGET/mariadb/dump
regardless of where the script itself is deployed.

Also drop the healthcheck integration (HEALTHCHECK_URL, send_healthcheck,
curl requirement) from borg-backup.sh per request - no monitoring hook
wanted for now.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
kbe
2026-07-25 21:30:17 +02:00
co-authored by Claude Sonnet 5
parent b8564703bc
commit dd4fd8cb9c
3 changed files with 11 additions and 8 deletions
+4 -5
View File
@@ -50,14 +50,13 @@ Run once, by hand, on the server:
## 2. Deploying the Scripts
Copy `borg-backup.sh`, `dump_db.sh`, and `restore.sh` to the server (e.g.
`/opt/backup-agent/`), and `dump_db.sh` additionally to
`/home/srv/files/content/mariadb/dump_db.sh` (this exact path is what
`borg-backup.sh` invokes). Make all three executable:
Copy `borg-backup.sh`, `dump_db.sh`, and `restore.sh` to `/opt/backup-agent/`
(this exact path is what `borg-backup.sh` invokes for `dump_db.sh`). Make
all three executable:
```bash
chmod +x /opt/backup-agent/borg-backup.sh /opt/backup-agent/restore.sh
chmod +x /home/srv/files/content/mariadb/dump_db.sh
chmod +x /opt/backup-agent/dump_db.sh
```
## 3. Scheduling