Part 2 of 5 · 1 min read
Full and incremental backups
A full backup copies everything; an incremental backup copies only what changed since the last backup.
Think of photocopying an entire filing cabinet's contents once a month, versus photocopying only the specific pages that were added or changed since the last photocopying session.
In plain words: a full backup copies the entire database's data at a specific point in time, while an incremental backup copies only the changes made since the previous backup, whether that previous backup was full or itself incremental. A full backup is simpler to restore from, since it is self-contained, but takes longer to create and more storage to keep. An incremental backup is faster to create and smaller, but restoring from it requires applying it on top of the full backup, and any incremental backups, that came before it, in the correct order.
A worked example. A full backup taken on Sunday captures the entire database; a Monday incremental backup captures only Monday's changes, meaning restoring to Monday's end requires applying Sunday's full backup first, then Monday's incremental backup on top of it.
The key lines. No new SQL; backups are typically taken with a dedicated database utility or command, separate from ordinary transaction statements.
Full backup, incremental backup
A full backup copies the entire database at a point in time; an incremental backup copies only the changes since the previous backup, requiring the prior backups to be restored first, in order, to reconstruct a full state.
Example: photocopying an entire filing cabinet once a month is a full backup; photocopying only the pages changed since the last session is an incremental backup.