Implement backup strategy for Longhorn volumes and databases #32

Open
opened 2026-07-25 19:37:17 +00:00 by lab · 0 comments
Owner

No backup strategy is documented or implemented.

What needs backing up

  1. Longhorn volumes — configure Longhorn backup to NFS/S3
  2. MySQL (CrowdSec, Homarr) — scheduled mysqldump cronjob
  3. PostgreSQL (Forgejo via CNPG) — CNPG has built-in backup, configure it
  4. External MariaDB (K3s datastore on bare metal) — mysqldump cronjob
  5. Authelia/lldap — backup PVC data

Steps

  1. Configure Longhorn backup target (NFS or S3-compatible)
  2. Create a CronJob for MySQL dumps → store in Longhorn PVC or NFS
  3. Configure CNPG backup for Forgejo PostgreSQL
  4. Document the backup/restore procedure in README
No backup strategy is documented or implemented. ## What needs backing up 1. **Longhorn volumes** — configure Longhorn backup to NFS/S3 2. **MySQL** (CrowdSec, Homarr) — scheduled mysqldump cronjob 3. **PostgreSQL** (Forgejo via CNPG) — CNPG has built-in backup, configure it 4. **External MariaDB** (K3s datastore on bare metal) — mysqldump cronjob 5. **Authelia/lldap** — backup PVC data ## Steps 1. Configure Longhorn backup target (NFS or S3-compatible) 2. Create a CronJob for MySQL dumps → store in Longhorn PVC or NFS 3. Configure CNPG backup for Forgejo PostgreSQL 4. Document the backup/restore procedure in README
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lab/homelab#32
No description provided.