Backup and Recovery Concepts: Failures, RPO and RTO

Oracle DBA Certification 12 min min read Updated: Nov 16, 2026 Beginner
Backup and Recovery Concepts: Failures, RPO and RTO
Beginner Topic 1 of 8

The DBA's Most Important Job

Everything else can be fixed later, but lost data cannot. A good DBA is judged by one question: *can you get the data back?* A backup you have never restored is only a hope, not a backup.

Types of Failures

FailureExampleFix
Statement failureInsert violates a constraintOracle rolls back the statement. Fix the SQL.
User process failureClient crashesPMON cleans up automatically
User errorSomeone drops a table or deletes dataFlashback, or point-in-time recovery
Instance failureServer power cut, memory crashSMON recovers at next startup using redo
Media failureDisk dies, datafile deletedRestore from backup, then recover using redo
DisasterData center lostStandby database, offsite backups

Restore vs Recover

WordMeaning
RestoreCopy files back from the backup
RecoverApply redo to bring them up to date
Simple example: Your document gets corrupted. Restore means opening last night's saved copy. Recover means redoing the edits you made since then using your typing history (redo).

Backup Types

TypeMeaning
Cold (consistent) backupDatabase is shut down. Simple but needs downtime.
Hot (online) backupDatabase is running. Needs ARCHIVELOG mode.
Full backupCopies all used blocks
Incremental level 0Same as full, the base for incrementals
Incremental level 1Only blocks changed since the last backup
Logical backupData Pump export of objects and rows
Physical backupRMAN copies of datafiles

RPO and RTO

TermQuestionExample
RPO (Recovery Point Objective)How much data can we afford to lose?At most 15 minutes
RTO (Recovery Time Objective)How long can we be down?At most 2 hours

Your backup plan is built from these two numbers. A tiny RPO needs archived redo kept safe or a standby database. A tiny RTO needs fast restore storage or standby.

A Typical Strategy

WhenWhat
SundayIncremental level 0 (full)
Monday to SaturdayIncremental level 1
Every 15-60 minutesBack up archived redo logs
MonthlyTest a full restore on another server
The 3-2-1 rule: Keep 3 copies of your data, on 2 different kinds of storage, with 1 copy off-site.
Never skip this: Test restores regularly. Many companies discover their backups are unusable only on the day they need them.

Conclusion

Know your failure types, choose RPO and RTO with the business and build a backup plan that you actually test.

Quick Summary: Restore = copy files back, recover = apply redo. RPO is data loss, RTO is downtime.

Get Newsletter

Subscibe to our newsletter and we will notify you about the newest updates on Edugators