Erich Blume ad7e9af453 Trim operational content from reference cards

Reference docs should describe "what things are", not "how to do things".
Removed:
- CLI command examples
- Operational workflows (PR workflow, sync commands)
- Setup/bootstrap procedures
- "Useful Commands" sections

Also split hosts.md into individual cards:
- infrastructure/indri.md - Primary server details
- infrastructure/gilbert.md - Development workstation

This content belongs in how-to guides (future phase).

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2026-02-03 13:44:26 -08:00

1.8 KiB

Raw Blame History

title

Backup Policy

Daily automated backups from infrastructure/indri to storage/sifaka NAS.

Schedule

Time	Frequency	System
2:00 AM	Daily	[[services/borgmatic

What Gets Backed Up

Directories

Path	Description	Priority
`~/code/personal/zk`	Zettelkasten notes	Critical
`/opt/homebrew/var/forgejo`	Git repositories	Critical
`~/.config/borgmatic`	Backup config	High
`~/Documents`	Personal documents	High
`~/Pictures`	Photos	Medium

Databases

Database	Host	Method
miniflux	[[services/postgresql	pg.ops.eblu.me]]
teslamate	[[services/postgresql	pg.ops.eblu.me]]

What Is NOT Backed Up

Data	Reason
ZIM archives (`~/transmission/`)	Re-downloadable via torrent
Prometheus metrics	Ephemeral, in k8s PVC
Loki logs	Ephemeral, in k8s PVC
devpi cache	Re-fetchable from PyPI

Retention Policy

Period	Retention
Daily	7 backups
Monthly	12 backups
Yearly	1000 backups

Backup Target

Repository: /Volumes/backups/borg/ on storage/sifaka

Monitoring

Metrics exposed to services/prometheus:

borgmatic_up - Repository accessible
borgmatic_last_archive_timestamp - Last backup time
borgmatic_repo_deduplicated_size_bytes - Disk usage

Dashboard: "Borgmatic Backups" in services/grafana

services/borgmatic - Backup system details
storage/sifaka - Backup storage
services/postgresql - Database backups

1.8 KiB Raw Blame History