Backup & Recovery (Rsync/Tar/Dd)

Stop your backups from silently truncating huge sparse files

🧩 The Challenge

Dealing with virtual machine images or database snapshots is a nightmare when you realize your backup tool decided to expand every zero-byte block into actual disk space. You end up with a 10GB archive that should have been a few megabytes, and suddenly your offsite storage is screaming about being full.

💡 The Fix

Use the sparse file handling flags to make sure your backup tool realizes that those empty chunks of data don’t actually need to occupy physical storage on the destination. It saves space and makes the transfer finish way faster.

rsync -av --sparse /path/to/source/ /mnt/backup/destination/

⚙️ Why It Works

Passing the –sparse flag forces rsync to detect long runs of zero bytes and write them as holes in the destination file rather than filling them with actual null characters. It’s the only way to avoid blowing up your quota when dealing with VM disk images or large log sparse files.

🚀 Pro-Tip: Always run a diff check after your first sparse transfer just to make sure the filesystem overhead isn’t lying to you.

Linux Tips & Tricks | © ngelinux.com | 10/6/2026