Table of Contents
When you back up a system, one question shapes almost everything else: does the system stay running during the backup, or not? That’s the difference between a hot backup (taken while the system is online) and a cold backup (taken while it’s offline). Each involves a real trade-off between availability, simplicity, and consistency. This article compares them and helps you choose.
What is a cold backup?
A cold backup — also called offline or static backup — is taken while the application, database, or VM is shut down or powered off. Because nothing is being written during the backup, you get a clean, fully consistent copy at a single point in time, with no risk of capturing data mid-change.
The trade-off is obvious: the system is unavailable for the duration of the backup. That makes cold backups a natural fit for workloads that can tolerate a maintenance window — overnight batch systems, or environments with defined off-hours.
Advantages
- Guaranteed consistency. With the system offline, the backup captures a stable, coherent state — no in-flight transactions to worry about.
- Simplicity. No special agents or techniques are needed to keep a running system consistent; it’s straightforward to perform and to restore.
Disadvantages
- Downtime. The system must be offline throughout, disrupting normal operations.
- Coarser recovery points. Because cold backups run during scheduled windows, your recovery points are less frequent — meaning potentially more data lost between them.
What is a hot backup?
A hot backup — also called online or dynamic backup — is taken while the system stays running and available to users. This is the standard approach for anything that can’t afford downtime, which today is most production infrastructure.
The challenge a hot backup has to solve is consistency: how do you copy data that’s actively changing? Two mechanisms make it reliable:
- Snapshots capture a point-in-time image of the running system to back up from, while it keeps operating.
- Application consistency. The backup briefly quiesces the application or database — via VSS on Windows, or a guest/database agent — so the captured state is clean and immediately usable, not just a “crash-consistent” copy. Databases can also use log-based online methods (such as Oracle’s ARCHIVELOG mode or MySQL binlogs), but application-aware, snapshot-based backup is the norm in virtualized environments.
Advantages
- No downtime. The system stays available throughout — essential for 24/7 operations and multi-user systems.
- More frequent recovery points. Hot backups can run often, keeping your recovery point close to the moment of failure.
- Broad coverage. Modern hot backup captures whole VMs, applications, and databases in a consistent state.
Disadvantages
- More complexity. Ensuring application consistency requires the right agents or integration — handled well by a proper backup solution, but not “free.”
- Resource use. Running backups against live systems consumes some I/O and storage, so scheduling and efficiency (incrementals, dedup) matter.
Cold vs. hot backup at a glance
| Cold backup | Hot backup | |
|---|---|---|
| System state | Offline / powered off | Online / running |
| Availability during backup | Unavailable (downtime) | Available |
| Consistency | Inherent (nothing changes) | Via snapshots + application consistency |
| Recovery points | Less frequent (windows) | Frequent |
| Complexity | Simple | Higher (needs consistency handling) |
| Best for | Workloads that tolerate downtime | Production, 24/7, minimal-downtime needs |
Which should you choose?
It comes down to your tolerance for downtime and how current your recovery point must be — in other words, your RTO and RPO. If a workload can be taken offline and you value simplicity and guaranteed consistency, cold backup is fine. If it must stay available and you need frequent, recent recovery points, hot backup is the answer — which is why it dominates modern virtualized environments. (See our guide to [RTO and RPO] for setting those targets.)
Beyond hot vs. cold: keep the copy safe
One clarification worth making, because it’s often muddled: the security of a backup doesn’t come from whether it’s hot or cold — it comes from where the copy lives. A backup on the same server as the source is vulnerable no matter how it was taken. The real protection against ransomware and disaster is keeping copies offsite, immutable, or air-gapped, following the 3-2-1-1-0 rule (three copies, two media, one offsite, one immutable/offline, zero recovery errors). Hot or cold, an untouchable copy is what gets you back after an attack. (More in our post on [snapshots and backups].)
How Storware fits
Storware Backup and Recovery performs online, application-consistent backups of running VMs, applications, and databases — using snapshots and quiescing to capture a clean state with minimal disruption — across every platform you run (VMware, Proxmox, Nutanix AHV, Hyper-V, OpenStack and more). It pairs that with incremental backups, deduplication, and immutable, air-gapped backup targets for ransomware resilience, under a single universal license — so you get the availability of hot backup and the safety of an untouchable copy.
Ready to protect your data?
Conclusion
Cold and hot backups sit at two ends of one trade-off: cold backups take the system offline for a simple, guaranteed-consistent copy; hot backups keep it running and rely on snapshots and application consistency to protect live data without downtime. Choose based on how much downtime you can tolerate and how recent your recovery point must be — and whichever you use, make sure at least one copy is immutable or offline, because availability during backup means nothing if the copy itself isn’t safe.
