Files
notes/docs/home-server/operations.md
T
2026-10-06 16:33:29 +01:00

2.1 KiB

schema_version, id, type, scope, sensitivity, last_reviewed, sources, related, update_triggers, unknowns
schema_version id type scope sensitivity last_reviewed sources related update_triggers unknowns
1 home-server.operations reference
jupiter
mercury
design-decisions
monitoring
recovery
private-infrastructure 2026-10-06
kind reference
owner-report RAID/media tradeoff, CGNAT/public IPv4 rationale, no alerting and running monitoring/log containers, 2026-10-06
home-server.reference
home-server.host
home-server.mercury
home-server.networking
home-server.storage
home-server.backups
home-server.deployment
data-priority-change
architecture-change
alerting-change
recovery-test
acceptable-downtime-and-data-loss-by-service
data-criticality-outside-the-four-backed-up-directories
tested-full-host-recovery-order
monitoring-review-frequency

Operations / decisions

Owner decisions

Decision Reason / accepted tradeoff
RAID 0 for HDD data Capacity prioritized over disk redundancy; downloaded media can be reacquired
Back up important state Four application directories covered; media redundancy is not the objective
Mercury public edge Static public IPv4; home ISP uses CGNAT
No residential public ingress Owner preference to avoid exposing the home IP

RAID 0 still stores important state alongside media: either HDD failure loses the array; recovery depends on working backups. Owner intent is not evidence that every important dataset is covered.

Observability

Facility Current configuration
Host/container monitoring Beszel hub and host-network agent present
Container logs Dozzle with Docker socket proxy present
Automatic alerting None configured

Monitoring does not imply notification delivery. Backup-hook failures, stopped services and storage failures require manual detection.

Recovery status

No restore test performed. Backup scope is documented in Backups; OS, host configuration and named-volume coverage must not be inferred from the four-directory plan. Recovery priorities, RPO/RTO and validated bootstrap instructions remain unconfirmed.