backup interval
How often backups are taken, such as hourly or nightly, which sets the most data you could lose between one backup and the next.
In more detail
The worst case is a failure just before the next backup runs, so the loss can approach one full interval, and the interval must therefore be no longer than the recovery point objective. What counts is what the backup system is really configured to do and succeeding at, not what the policy says. Where backups cannot run often enough, databases close the gap with transaction logs or replication.
Examples
identity: RPO 4h, backup every 24h could lose 24h of dataEVERY = timedelta(hours=4) # backup scheduleRelated terms
- RPO — Recovery point objective, the most data a business can afford to lose in an outage, measured as the time before the failure.
- 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.
- incremental backup — A backup that saves only what changed since the previous backup of any kind, full or incremental.
- 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.
Taught in
- Business Impact Analysis, RTO & RPO Modeling — Cybersecurity Fundamentals, GRC & Cryptography
- Backup Architectures: 3-2-1, Immutability & Air-Gaps — Cybersecurity Fundamentals, GRC & Cryptography