restore test
Actually recovering data or a system from a backup to prove the backup works and to measure how long recovery takes.
In more detail
A backup that has never been restored is only a hope: files can be missing, corrupted, encrypted with a key nobody can reach, or far too slow to bring back. A restore test brings the data back somewhere safe, checks it is correct by comparing hashes or running a query, and records the real restore time. That measured time, not a guess, is what you compare with the recovery time objective.
Examples
sqlite3 restored.db "SELECT id, email FROM customer;"manifest = {n: sha256("restore/" + n) for n in sorted(os.listdir("restore"))}Related terms
- backup — An extra copy of data kept separately so it can be restored if the original is lost, damaged, deleted or encrypted by an attacker.
- RTO — Recovery time objective: how long the business can accept a service being down before it is restored.
- 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.
- disaster recovery — The planned, tested procedure for getting a system and its data back after a serious failure, such as lost storage or a deleted cluster.
Taught in
- Defense-in-Depth & Security Control Categories — Cybersecurity Fundamentals, GRC & Cryptography
- Security Frameworks: NIST CSF 2.0, ISO 27001 & CIS — Cybersecurity Fundamentals, GRC & Cryptography
- Data States: Security at Rest, in Transit, and in Use — Cybersecurity Fundamentals, GRC & Cryptography
- Business Impact Analysis, RTO & RPO Modeling — Cybersecurity Fundamentals, GRC & Cryptography
- Disaster Recovery Sites: Hot, Warm & Cold — Cybersecurity Fundamentals, GRC & Cryptography
- Backup Architectures: 3-2-1, Immutability & Air-Gaps — Cybersecurity Fundamentals, GRC & Cryptography