Skip to content

Backup Strategy - Complete Documentation

Last Updated: YYYY-MM-DD Status:

This document describes the complete backup strategy for the homelab.

Philosophy

If it's not documented, it does not exist. If it's not backed up, it will be lost. If it's not tested, it won't work when you need it.

Backup Layers

Layer 1: Local Snapshots

  • ZFS/BTRFS snapshots on storage server
  • Protects against: accidental deletion, file corruption
  • Not a backup: Still on same hardware

Layer 2: VM/Application Backups

  • Hypervisor VM backups to storage server
  • Application automated backups (HA, Nextcloud, etc.)
  • Protects against: VM corruption, misconfiguration, service failure

Layer 3: Offsite Storage

  • Cloud object storage (B2, Storj, S3, etc.)
  • Protects against: hardware failure, fire, theft, natural disaster

Layer 4: Documentation

  • This repository (markdown files)
  • Recovery procedures and configuration details
  • Critical: Without docs, you can't rebuild

Hypervisor Backup Configuration

Storage Setup

Backup destination: - Server: - Path: - Quota:

Security:

Backup Schedule

Setting Value
Schedule
VMs included
Retention
Compression
Mode

Storage Server Config Backup

Current Status

  • Status:
  • Frequency:

Offsite Backup Configuration

Backup Destination 1

Setting Value
Provider
Schedule
Grace period
Monitoring

What syncs:

Backup Destination 2 (if applicable)

Setting Value
Provider
Schedule
Grace period

What syncs:

Application Backups

Home Assistant

  • Method:
  • Schedule:
  • Destination:

Photo Library (Immich)

  • Data:
  • Offsite:

File Sync (Nextcloud)

  • Data:
  • Offsite:

Monitoring

All backup tasks should be monitored. See monitoring.md.

Recovery Procedures

Testing Schedule

Monthly

  • [ ] Verify backups are running
  • [ ] Check backup storage space usage
  • [ ] Verify offsite sync completing

Quarterly

  • [ ] Full VM restore test
  • [ ] Test offsite data retrieval
  • [ ] Verify data integrity

Annually

  • [ ] Full disaster recovery simulation
  • [ ] Update all documentation
  • [ ] Review retention policies
  • [ ] Review offsite backup costs

Important Notes

  • Power management: Schedule backups when servers are running
  • Network security: Restrict NFS/backup access to specific IPs
  • Storage quota: Set limits to prevent runaway disk usage
  • Task coordination: Stagger backup tasks to avoid conflicts
  • Philosophy: Better to have backups we don't need than need backups we don't have

Last manual backup verification: Last restore test: Last disaster recovery drill: