Backup & Recovery (Rsync/Tar/Dd)

Stop letting your backups get corrupted by bit rot while you sleep

🧩 The Challenge

You finally moved that massive archive to long-term storage, but six months later you try to pull a file and it’s just total garbage. I’ve been burned by silent bit rot more times than I care to admit, and finding out your backup is toast only when you need it most is a nightmare.

💡 The Fix

Use a checksum manifest when you create your tarballs so you can verify the integrity of the data anytime later. It takes a few extra seconds now, but it saves your bacon when you need to prove your files haven’t drifted.

tar -cvf backup.tar /data/important && find /data/important -type f -exec sha256sum {} + > manifest.sha256

⚙️ Why It Works

This approach records the fingerprint of every file at the moment of backup, allowing you to run a quick integrity check against the original set later on. By generating these hashes during the archival process, you eliminate the guesswork when verifying your recovery points.

🚀 Pro-Tip: Pipe your verification check into sha256sum –check to immediately flag any file that has drifted by even a single bit.

Linux Tips & Tricks | © ngelinux.com | 8/25/2026