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/rest-server-nh3/README.md
+1 -1
View File
@@ -6,7 +6,7 @@ NH3-site restic backup endpoint. Runs in Synology Container Manager on `10.100.5
**Port:** `http://10.100.50.50:8000` (configurable via `.env`)
**Data:** `/volume1/Backup/restic/` (configurable)
Paired with the existing `restic rest-server` on **ana-docker** (`http://10.250.50.70:8000`, data on TrueNAS NFS) as the Anaheim-side endpoint. Each fleet host backs up to the rest-server closest to it; an rsync job on ana-docker mirrors the two trees against each other for off-site redundancy.
Paired with `rest-server-ana` on **ana-docker** (`http://10.250.50.70:8000`, data on an NFS mount backed by the Debian file server at `10.250.50.50`) as the Anaheim-side endpoint. Each fleet host backs up to the rest-server closest to it; an rsync job on ana-docker mirrors the two trees against each other for off-site redundancy.
## Auth model