backup chain
The ordered set of backups, a full one plus later incrementals, that must all be present and intact to restore to a given point.
In more detail
Incremental backups only make sense together, each building on the one before. A restore replays them in order on top of the full backup, so a single missing or corrupted link loses every change after it. Long chains restore slowly and carry more risk, which is why teams take a fresh full backup regularly and test restores from the end of the chain.
Related terms
- incremental backup — A backup that saves only what changed since the previous backup of any kind, full or incremental.
- full backup — A backup that copies all of the selected data every time, whatever has changed since the last one.
- restore test — Actually recovering data or a system from a backup to prove the backup works and to measure how long recovery takes.
- manifest.json — A file written at backup time that lists every backed-up file with its SHA-256 digest, so a restore can be checked byte for byte.
Taught in
- Backup Architectures: 3-2-1, Immutability & Air-Gaps — Cybersecurity Fundamentals, GRC & Cryptography