From b8e2ac80c355c3663994eb991d6918dc382be623 Mon Sep 17 00:00:00 2001 From: Stefan Koelle Date: Fri, 11 Sep 2026 22:46:05 +0200 Subject: [PATCH] Reduce redundancy: LED Matrix dup, 3-2-1 wording, Synology SHR --- infra/backup-strategy/index.njk | 2 +- infra/index.njk | 2 +- infra/synology/index.njk | 6 +++--- stefankoelle/index.njk | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/infra/backup-strategy/index.njk b/infra/backup-strategy/index.njk index aac5b3e..ebdc4ee 100644 --- a/infra/backup-strategy/index.njk +++ b/infra/backup-strategy/index.njk @@ -11,7 +11,7 @@ layout: base.njk

The homelab uses a layered backup approach, split into two independent tracks: NAS user content, and Proxmox VM/LXC backups. Both follow a -3-2-1-style rule, multiple copies, multiple media types, at least one +3-2-1-style rule: multiple copies, multiple media types, and at least one copy on a different machine.

NAS user content, four layers

diff --git a/infra/index.njk b/infra/index.njk index 043f35c..9839128 100644 --- a/infra/index.njk +++ b/infra/index.njk @@ -42,7 +42,7 @@ sections:

The setup at a glance

The infrastructure runs on three main machines: a Proxmox VE host (Beelink S12 Pro, 32GB 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.

+

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 layered strategy: local snapshots, NAS copies, offsite sync to a Raspberry Pi in a different room, and cloud archive for worst-case scenarios.

Why Proxmox

Proxmox VE was chosen over alternatives like ESXi or plain Docker for several reasons. The open-source model means no licensing headaches. LXC containers provide near-native performance for lightweight services without the overhead of full VMs. The web UI makes it easy to manage snapshots, backups, and migrations. And the ZFS support on the underlying Debian system gives us reliable snapshots and send/receive for the backup chain.

diff --git a/infra/synology/index.njk b/infra/synology/index.njk index f1d835a..247a9fd 100644 --- a/infra/synology/index.njk +++ b/infra/synology/index.njk @@ -13,8 +13,8 @@ layout: base.njk

Storage

@@ -29,7 +29,7 @@ layout: base.njk diff --git a/stefankoelle/index.njk b/stefankoelle/index.njk index 3604615..04f0fad 100644 --- a/stefankoelle/index.njk +++ b/stefankoelle/index.njk @@ -197,7 +197,7 @@ layout: stefankoelle.njk

Arduino / PlatformIO