vh/esh-pfi-infrastructure
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

Correct Ana-side NAS identity: Debian 12, not TrueNAS

Browse Source 
Network probes (no web admin, Debian SSH banner, only file-server ports
open) show 10.250.50.50 is vanilla Debian 12 with hand-configured NFS/SMB,
reprovisioned from the original TrueNAS SCALE install. Update stack
comments, README storage notes, Backrest description, proxmox-vms.md
entry for VM 100, and the restic configs intro to match.

Cross-site sync plan simplifies to plain rsync over SSH on both sides —
no appliance-specific tooling needed.
This commit is contained in:
vh
2026-04-20 14:36:07 -07:00
parent b443b5c220
commit f6b0e2b22f
8 changed files with 24 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files
stacks/backrest/README.md
+4 -4
View File
@@ -7,7 +7,7 @@ Web UI over restic repositories. Runs **once, on ana-docker**, and points at eve
## Role in the fleet
- Actual backups are run by per-host `systemd` timers calling `restic` (see the backup design; not yet deployed). Each host writes to its site-local S3 bucket (TrueNAS on ana, Synology on nh3).
- Actual backups are run by per-host `systemd` timers calling `restic`. Each host writes to its site-local rest-server (ana-docker for Anaheim hosts, Synology for NH3).
- **This container does not run backups by default** — it's a viewer/manager pointed at existing repos. (Backrest *can* be the scheduler instead of systemd timers; we're keeping the scheduler on the host for simplicity.)
- Because it only needs to talk to S3 endpoints (not host filesystems), no bind mounts of host paths are required.
@@ -44,9 +44,9 @@ For each per-host repo (to be added once the restic pipeline is running):
## Backup scope, when wired up
- ana-docker, ana-ml2 → TrueNAS S3 at `10.250.50.50:4521`
- nh3-docker, esh-docker-vm → Synology S3 at `10.100.50.50:4521`
- Cross-site rclone sync makes each bucket also hold the other site's data, so you can restore *either* host from *either* side if one NAS is down.
- ana-docker, ana-ml2, esh-docker-vm → Anaheim rest-server on ana-docker (`:8000`), data on NFS mount backed by the Debian file server at `10.250.50.50`
- nh3-docker → NH3 rest-server on the Synology (`10.100.50.50:8000`), data on local Btrfs
- Cross-site rsync will make each NAS hold the other site's data, so you can restore *either* host from *either* side if one NAS is down.
## Scaling knobs