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-ana/README.md
+2 -2
View File
@@ -4,7 +4,7 @@ Anaheim-site restic backup endpoint. Replaces the older `restic` stack on ana-do
**Server:** ana-docker (`10.250.50.70`)
**Port:** `http://10.250.50.70:8000`
**Data:** `/mnt/backup/restic/repo/ana/` (TrueNAS NFS mount on the host)
**Data:** `/mnt/backup/restic/repo/ana/` (NFS mount on the host, served by the Debian file server at `10.250.50.50`)
Paired with:
- **`rest-server-nh3`** on the Synology (`10.100.50.50:8000`, data on Btrfs).
@@ -23,7 +23,7 @@ Paired with:
| image version | floating `latest` | `${REST_SERVER_VERSION}` |
| stack dir on server | `/opt/docker/compose/restic/` | `/opt/docker/compose/rest-server-ana/` |
Data path is unchanged (`/mnt/backup/restic/repo/ana/`) so nothing new needs to be allocated on TrueNAS.
Data path is unchanged (`/mnt/backup/restic/repo/ana/`) so nothing new needs to be allocated on the NAS.
## Pre-deploy: clean the data dir and create htpasswd