---
schema_version: 1
id: home-server.operations
type: reference
scope: [jupiter, mercury, design-decisions, monitoring, recovery]
sensitivity: private-infrastructure
last_reviewed: "2026-10-06"
sources:
  - kind: owner-report
    reference: "RAID/media tradeoff, CGNAT/public IPv4 rationale, no alerting and running monitoring/log containers, 2026-10-06"
related: [home-server.reference, home-server.host, home-server.mercury, home-server.networking, home-server.storage, home-server.backups, home-server.deployment]
update_triggers: [data-priority-change, architecture-change, alerting-change, recovery-test]
unknowns:
  - 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](backups.md);
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.