Course contentsShow
← System Design
Lesson 1425 of 1,91935. Backup and Disaster RecoveryFree lesson

Hot vs Cold vs Warm Backups

Trading off between online backups during operation, offline backups requiring downtime, and snapshot-based approaches.

Hot vs Cold vs Warm Backups

What you'll learn: How to trade off between online backups during operation, offline backups requiring downtime, and snapshot-based hybrid approaches.

The Core Tradeoff

When creating backups, you face a fundamental tension: do you back up data while the system runs (hot), shut it down first (cold), or take a middle path (warm)? Each approach balances consistency, availability, and operational complexity differently.

Hot Backups (Online)

Hot backups run while your application actively serves traffic. Think of it like photocopying documents while people are still writing on them—you might catch pages mid-update.

  • Pros: Zero downtime, no service interruption
  • Cons: Risk of inconsistent state (e.g., half-committed transactions), requires coordination mechanisms
  • Use when: Downtime is unacceptable (e-commerce, social platforms)

Cold Backups (Offline)

Cold backups require stopping the application completely before backup begins. Like closing a store to count inventory—accurate, but customers wait.

  • Pros: Perfect consistency, simple to implement
  • Cons: Requires downtime window, impacts availability
  • Use when: Consistency is critical and scheduled maintenance windows are acceptable

Warm Backups (Snapshot-Based)

Warm backups use quick snapshots or brief pauses to capture a consistent point-in-time state without full shutdown. Like pressing pause on a video game to save—quick freeze, then resume.

  • Pros: Minimal disruption (seconds), good consistency
  • Cons: Still requires brief coordination, depends on storage snapshot features
  • Use when: You need consistency but can afford only brief pauses

Choosing Your Approach

Your RPO and RTO requirements guide this decision. Hot backups suit low-RPO needs but may complicate recovery. Cold backups guarantee clean state but extend RTO with longer maintenance windows.

Key Takeaway: Hot backups prioritize availability over consistency guarantees, cold backups do the opposite, and warm backups split the difference with snapshot technology—choose based on your downtime tolerance and consistency requirements.