Tag: backup

BorgBackup is great. Borgmatic makes you actually run it: config-driven schedules, hooks, healthchecks, and a backup system that pages you when it breaks.

Your cluster will fail. Velero captures everything — manifests, CRDs, persistent volumes — and lets you replay it on a fresh cluster. Setup, gotchas, real DR plans.

Borg is open-source classic with SSH targets. Duplicacy has lock-free multi-source magic but commercial GUI. Here's which backup tool to pick.

rclone copies and syncs files to cloud storage. Restic does deduplicated encrypted snapshots. Confusing them costs you restores at 2 AM.

Restic, Borg, and Kopia all deduplicate and encrypt — but differ on backends, compression, and UI. Pick the right backup tool for your Linux home lab.

Restic forget, prune, and check: right order, real retention flags, cron automation, and why --read-data on a large repo will ruin your whole weekend.

Stop burning money on AWS egress fees. Here is how to build a real tiered backup strategy using Backblaze B2 plus rclone for your home lab setup in 2026.

Set up Snapper on Btrfs to auto-snapshot before every system update, roll back broken machines in minutes, and never lose a working root filesystem again.

sanoid manages ZFS snapshot policies automatically, syncoid replicates them over SSH to remote pools — together they're the lowest-effort offsite backup strategy for any ZFS user.

Stop letting every machine write directly to S3. Kopia repository server gives you shared dedup, per-host auth, and sane maintenance — all in one place.

Build a real disaster recovery plan for your home lab: RTO/RPO explained simply, 3-2-1 backup rule, Proxmox backups, Restic to Backblaze B2, and a runbook template you'll actually use.

You've got backups. Great. But do you know if they actually work? RTO and RPO mean nothing if you've never actually restored.