Keep the home server's root backup scripts with the rest of its tooling
This commit is contained in:
1 parent
7cc98cd318
commit
042885f113
3 files changed
+326
-3
No files matched your search
+5
-3
@@ -129,9 +129,11 @@ them.
|
||||
- `home/RESTORE.md`: how to restore the home server's `~/Server` from the
|
||||
ZFS backup.
|
||||
- `home/backup` and `home/systemd/`: the home server's backup trigger and its
|
||||
root system units (`server-backup` nightly, `media-backup` weekly). The
|
||||
scripts those units run live in `/usr/local/sbin` on that machine. They are
|
||||
readable by root alone, so this tree has no copy of them.
|
||||
root system units (`server-backup` nightly, `media-backup` weekly).
|
||||
- `home/server-backup` and `home/media-backup`: the scripts those units run.
|
||||
On that machine they live in `/usr/local/sbin`, root-owned, because a
|
||||
root-run script must not sit in a directory the user can write to. Restore
|
||||
them there, not into `~/Server`.
|
||||
|
||||
The VPS units carry `RequiresMountsFor=/home/gib/Media` because that host
|
||||
keeps its podman graphroot on an attached volume mounted there. The setting
|
||||
|
||||
Reference in new issue
Block a user