Add Unraid flash config to Borg preflight
This commit is contained in:
@@ -17,7 +17,7 @@ It should **not** be implemented as a Borg UI inline hook in the current design.
|
||||
`pre-borg.sh` currently chains the host-side checks:
|
||||
|
||||
- `services/posture-check/posture-check.sh`
|
||||
- `ops/borg-ui/scripts/pre-backup-dumps.sh`
|
||||
- `ops/borg-ui/scripts/pre-backup-dumps.sh` including the Unraid flash config archive
|
||||
- `ops/restore-tests/check-restore-freshness.sh`
|
||||
|
||||
The dump step assumes:
|
||||
@@ -56,9 +56,10 @@ The intended sequence is:
|
||||
|
||||
1. Host wrapper checks posture.
|
||||
2. Host script refreshes `latest` dump artifacts.
|
||||
3. Freshness check verifies expected dumps.
|
||||
4. Borg UI backs up `/local/borg-dumps` together with the rest of `critical_infra`.
|
||||
5. Borg history preserves dump history, so the host only needs to keep the most recent dump set.
|
||||
3. Host script writes `unraid-flash-config.tar.gz` plus checksum and manifest into the same dump set.
|
||||
4. Freshness check verifies expected dumps and the flash config archive.
|
||||
5. Borg UI backs up `/local/borg-dumps` together with the rest of `critical_infra`.
|
||||
6. Borg history preserves dump history, so the host only needs to keep the most recent dump set.
|
||||
|
||||
## Current dump target
|
||||
|
||||
|
||||
Reference in New Issue
Block a user