From ffd1cd16214db9a6abc843cc69327f3d43612501 Mon Sep 17 00:00:00 2001
From: Stefan Koelle
Date: Fri, 11 Sep 2026 22:31:32 +0200
Subject: [PATCH] Unify Proxmox host as Beelink S12 Pro; remove false
monitoring-backup open item
---
infra/index.njk | 2 +-
infra/monitoring/index.njk | 1 -
infra/proxmox/index.njk | 2 +-
3 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/infra/index.njk b/infra/index.njk
index 846841c..97781cc 100644
--- a/infra/index.njk
+++ b/infra/index.njk
@@ -41,7 +41,7 @@ sections:
The setup at a glance
- The infrastructure runs on three main machines: a Proxmox VE host (Intel NUC, 64GB RAM) as the primary compute node, a Synology DS918+ NAS for storage and Docker services, and a Xubuntu VM on Proxmox for development. An OpenWrt router handles multi-WAN failover with WiFi and Powerline backhaul, and four Zyxel GS1200-8HP managed switches distribute the network across the flat.
+ The infrastructure runs on three main machines: a Proxmox VE host (Beelink S12 Pro, 64GB RAM) as the primary compute node, a Synology DS918+ NAS for storage and Docker services, and a Xubuntu VM on Proxmox for development. An OpenWrt router handles multi-WAN failover with WiFi and Powerline backhaul, and four Zyxel GS1200-8HP managed switches distribute the network across the flat.
The whole stack is monitored via Prometheus and Grafana, with node exporters on every machine, cAdvisor for container metrics, and SNMP exporters for network hardware. Backups follow a 3-2-1 strategy: local snapshots, NAS copies, offsite sync to a Raspberry Pi in a different room, and cloud archive for worst-case scenarios.
Why Proxmox
diff --git a/infra/monitoring/index.njk b/infra/monitoring/index.njk
index 7715475..b15d53a 100644
--- a/infra/monitoring/index.njk
+++ b/infra/monitoring/index.njk
@@ -52,7 +52,6 @@ temperature thresholds) are planned but not yet implemented.
Alerting rules are not yet configured for most services.
The secondary (test) Proxmox host isn't monitored yet, it's usually powered off.
Retention policy for Prometheus data hasn't been tuned.
-Monitoring data itself isn't currently backed up.
diff --git a/infra/proxmox/index.njk b/infra/proxmox/index.njk
index 87e97e3..2d594f9 100644
--- a/infra/proxmox/index.njk
+++ b/infra/proxmox/index.njk
@@ -13,7 +13,7 @@ layout: base.njk
Hardware
-- PVE (main server), a Beelink Mini-PC, running as the primary Proxmox host. It has a 500GB SSD for VM and container storage, and connects to the network via the server-room Zyxel switch.
+- PVE (main server), a Beelink S12 Pro, running as the primary Proxmox host. It has a 500GB SSD for VM and container storage, and connects to the network via the server-room Zyxel switch.
- pve2 (test server), a second Proxmox host, physically located in the study and connected via the OpenWRT-side Zyxel switch. It's dedicated purely to testing and development, running the third Docker host VM (docker-host-pve2) plus experimental setups without risking the production environment.
- Backups, nightly VM backups from PVE run at 00:30 to an NFS share on the Synology (
nas:/volume1/backup), with retention of the last 3 daily, 3 monthly and 1 yearly backup.