journaling
Recording each change in a log before applying it, so a system can recover cleanly or replay changes after a failure.
In more detail
Databases and many file systems write every change to a journal, also called a transaction log, before changing the main data. After a crash the log is used to finish or undo half-done work. Kept alongside backups, the same log lets you restore the last full backup and replay changes up to a chosen minute, which is point-in-time recovery.
Related terms
- point-in-time recovery — Restoring a database to its exact state at a chosen moment by loading a backup and replaying logged changes up to that moment.
- full backup — A backup that copies all of the selected data every time, whatever has changed since the last one.
- database — A program that stores data in an organised way and answers questions about it, such as PostgreSQL.
- RPO — Recovery point objective, the most data a business can afford to lose in an outage, measured as the time before the failure.
Taught in
- Backup Architectures: 3-2-1, Immutability & Air-Gaps — Cybersecurity Fundamentals, GRC & Cryptography