stefankoelle/moonweb-site
1
0
Fork 0
mirror of https://github.com/skoelle/moonweb-site.git synced 2026-09-17 17:00:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

Remove all em-dashes from website content and documentation

Browse Source 
Replace ' — ' with ', ' across 40 files. Hyphens (-) untouched.
timecapsule, stefankoelle, LICENSE, CSS comments left as-is.
This commit is contained in:
stefankoelle
2026-09-11 20:13:28 +02:00
parent 3363702ee6
commit eb0b777418
40 changed files with 311 additions and 311 deletions
Download Patch File Download Diff File Expand all files Collapse all files
infra/backup-strategy/index.njk
+7 -7
View File
@@ -11,10 +11,10 @@ layout: base.njk
<p>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, at least one
copy on a different machine.</p>
<h2>NAS user content — four layers</h2>
<h2>NAS user content, four layers</h2>
<table>
<tr><th>Layer</th><th>Target</th><th>Frequency</th><th>Purpose</th></tr>
<tr><td>Snapshots</td><td>Synology, built-in</td><td>Hourly</td><td>Fast recovery of accidentally deleted files</td></tr>
@@ -23,17 +23,17 @@ copy on a different machine.</p>
<tr><td>Cloud archive</td><td>Cloud storage</td><td>Continuous</td><td>Off-site copy for worst-case scenarios (fire, theft)</td></tr>
</table>
<h2>Proxmox VM/LXC backups — three copies, two machines</h2>
<h2>Proxmox VM/LXC backups, three copies, two machines</h2>
<table>
<tr><th>Copy</th><th>Target</th><th>Frequency</th></tr>
<tr><td>1 — original</td><td>Proxmox host itself</td><td>Daily</td></tr>
<tr><td>2 — primary offsite</td><td>Synology NAS (different machine)</td><td>Daily, right after copy 1</td></tr>
<tr><td>3 — secondary offsite</td><td>Raspberry Pi backup target, different room</td><td>Daily (skipped one day/week to avoid network contention with the weekly NAS sync)</td></tr>
<tr><td>1, original</td><td>Proxmox host itself</td><td>Daily</td></tr>
<tr><td>2, primary offsite</td><td>Synology NAS (different machine)</td><td>Daily, right after copy 1</td></tr>
<tr><td>3, secondary offsite</td><td>Raspberry Pi backup target, different room</td><td>Daily (skipped one day/week to avoid network contention with the weekly NAS sync)</td></tr>
</table>
<h2>Design principles</h2>
<ul>
<li>Backups always cross at least one machine boundary — nothing is considered "backed up" if it only lives on the source machine's local disk.</li>
<li>Backups always cross at least one machine boundary, nothing is considered "backed up" if it only lives on the source machine's local disk.</li>
<li>Weekly and daily jobs are scheduled to avoid saturating the internal power-line network link used by the offsite backup target.</li>
<li>All scheduled jobs ping a dead-man's-switch monitoring service; a missed backup triggers an alert.</li>
<li>Power to the offsite drive is only switched on for the duration of its weekly sync, to save power and extend disk life.</li>