Incremental Backups
What You'll Learn
You'll learn how incremental backups save storage and time by capturing only changed data, and why that efficiency comes with restoration complexity.
The Core Idea
After running a full backup (which copies everything), an incremental backup captures only the data that has changed since the last backup — whether that was a full or another incremental. Think of it like a diary: your full backup is the complete story up to day zero, and each incremental is just "what happened today" rather than retelling the entire story from the beginning.
This approach dramatically reduces:
- Storage requirements: You're not duplicating unchanged files repeatedly
- Backup window time: Copying 100 MB of changes beats copying 10 TB every night
- Network bandwidth: Especially critical for remote/cloud backups
The Restoration Tradeoff
Here's the catch: to restore your system, you must apply backups in order:
- Start with the most recent full backup
- Apply every incremental backup taken since then, in sequence
If you have a full backup from Sunday plus incrementals from Monday through Friday, a Friday restoration requires replaying all five incrementals. Lose Wednesday's incremental? Your restoration stops at Tuesday.
Analogy: It's like assembling a puzzle — the full backup gives you the base picture, but you need every incremental "piece" in order to see the complete current image.
Common Pattern
Many systems use a hybrid strategy:
- Weekly full backups
- Daily incrementals between full backups
- This limits restoration to at most 7 steps
Key Takeaway: Incremental backups optimize backup speed and storage by capturing only changes since the last backup, but they increase restoration complexity and create dependency chains that must be preserved carefully.