Correct Ana-side NAS identity: Debian 12, not TrueNAS
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:
@@ -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
|
||||
|
||||
|
||||
@@ -1,7 +1,9 @@
|
||||
# Backrest — web UI over restic repositories.
|
||||
#
|
||||
# Role here: single central viewer for every host's restic repo on both
|
||||
# site-local S3 endpoints (TrueNAS at ana, Synology at nh3). Per-host
|
||||
# site-local rest-servers (ana-docker writing to the Debian NFS server
|
||||
# at 10.250.50.50, Synology at 10.100.50.50 writing to its local Btrfs).
|
||||
# Per-host
|
||||
# `restic` runs will still be driven by systemd timers on each host; this
|
||||
# stack is how we see what ran, browse snapshots, and restore.
|
||||
#
|
||||
|
||||
@@ -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
|
||||
|
||||
|
||||
@@ -1,8 +1,9 @@
|
||||
# rest-server (Anaheim) — restic backup target for the fleet.
|
||||
#
|
||||
# Deploys to ana-docker. Data dir is on the TrueNAS NFS mount
|
||||
# (/mnt/backup/restic/repo/ana) so snapshots on the NAS side protect the
|
||||
# backup blobs themselves.
|
||||
# Deploys to ana-docker. Data dir is the NFS mount at
|
||||
# /mnt/backup/restic/repo/ana, backed by the Debian 12 NFS/SMB file
|
||||
# server at 10.250.50.50. (Historically a TrueNAS SCALE appliance; since
|
||||
# reprovisioned as vanilla Debian.)
|
||||
#
|
||||
# Mirrors stacks/rest-server-nh3/ in every meaningful way — same auth
|
||||
# model, same on-disk layout, same operational semantics — so each client
|
||||
@@ -50,7 +51,7 @@ services:
|
||||
- homepage.group=PFI-ANA
|
||||
- homepage.name=Restic (rest-server)
|
||||
- homepage.icon=mdi-cloud-upload
|
||||
- homepage.description=Anaheim restic endpoint (data on TrueNAS NFS)
|
||||
- homepage.description=Anaheim restic endpoint (data on NFS)
|
||||
- homepage.href=http://10.250.50.70:${REST_PORT}
|
||||
|
||||
networks:
|
||||
|
||||
@@ -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
|
||||
|
||||
|
||||
Reference in New Issue
Block a user