Disk Backup Runbook

Same procedure for both backup-local and backup-offsite. Both disks are identical replicas.

What is backed up:

Dataset	Encrypted on dest	Notes
`zpool0/family`	Yes (raw send)
`zpool0/vault`	Yes (raw send)
`zpool0/games`	No
`zpool0/pve-backup`	No
`zpool0/media/music`	No	Excluded from full media backup but included here due to irreplaceability

zpool0/media is excluded — too large for external disks and considered replaceable.

1. Create Snapshots

Snapshot name is set as a variable first so all commands use the exact same timestamp even if execution spans a second boundary.

SNAP="backup-$(date +%Y%m%d)"

zfs snapshot -r zpool0/family@$SNAP
zfs snapshot -r zpool0/vault@$SNAP
zfs snapshot -r zpool0/games@$SNAP
zfs snapshot -r zpool0/pve-backup@$SNAP
zfs snapshot -r zpool0/media/music@$SNAP

2. Replicate with Syncoid

Replace <target> with backup-local or backup-offsite.

# Encrypted datasets — raw send
syncoid --sendoptions="w" --no-sync-snap --recursive --no-rollback zpool0/family <target>/family
syncoid --sendoptions="w" --no-sync-snap --recursive --no-rollback zpool0/vault <target>/vault

# Unencrypted datasets
syncoid --no-sync-snap --recursive --no-rollback zpool0/games <target>/games
syncoid --no-sync-snap --recursive --no-rollback zpool0/pve-backup <target>/pve-backup
syncoid --no-sync-snap --recursive --no-rollback zpool0/media/music <target>/music

Flags: - --sendoptions="w" — raw send, preserves encryption on destination - --no-sync-snap — use existing snapshots, don't let syncoid create its own - --recursive — replicate all child datasets - --no-rollback — don't roll back destination on conflict (safer)

3. Clean Up Old Snapshots

Check first, then destroy.

# Check what would be deleted
zfs list -H -t snapshot -o name -r zpool0 | grep '@backup-20260101'

# Destroy when confirmed
zfs list -H -t snapshot -o name -r zpool0 | grep '@backup-20260101' | xargs -n1 zfs destroy

4. Export Pool Before Unplugging

zpool export <target>

Always export before physically disconnecting the disk.