Documentation Operations
OPERATIONS / TECHNICAL

Backups & recovery

Protect existing data and know which recovery path to use.

Baseline jobs

Adopt existing database and home-server image backup timers, health checks, and backup-status metric generation. Inspect the installed schedules and destinations before managing them.

Application rollback

The deployment stores versioned portal releases and the previous active target. Rollback reactivates a retained verified release and checks both the portal and Qwen connection. It must not overwrite application data.

Configuration recovery

Sensitive configuration snapshots are stored outside public Git. Restore only the affected files, validate them, and reload the relevant service. Preserve unrelated tunnel routes and the production AI environment.

Full-host recovery

Restore or install Ubuntu, establish network and SSH access, enroll the tunnel connector, then run the provisioning workflow. Model downloads and data restoration may require separate elapsed time.

Local backup panels

A dedicated dashboard uses existing home_server_backup and nutsnews_db_backup metrics for outcomes, attempt age, archive size, duration, cloud copies, and status freshness. Local alert rules surface failed backup outcomes and stale status collection without changing any backup jobs.

ON THIS PAGE

THREE WAYS TO UNDERSTAND

Same system.
Your level of detail.

Switch reading modes above to find the explanation that fits.

Explore Expert →

Keep exploring

Documentation that follows code

How release checks keep all three reading versions aligned with implementation.

Add another application

Extend the portal without changing the production AI contract.