What is a hot site?
A hot site is an alternate processing location that already runs a working copy of production. Servers, storage, network equipment and security tools are installed and powered on, and data is kept current by replication from the primary site. When the primary data center is lost, operations typically switch over in minutes to a few hours. It is the fastest type of recovery site and the most expensive, because the organization pays for a second environment every month whether or not a disaster ever happens.
How a hot site works
In an active/passive design, the hot site stands by with current replicas and takes over when a disaster is declared. In an active/active design, both sites carry live traffic all the time, so either can absorb the other's load; this is the same idea taken further. Replication can be synchronous, where a write is not confirmed until both sites have it, which is practical only over relatively short distances, or asynchronous, which allows long distances but means the hot site can lag by seconds or minutes.
A hot site can be a second company-owned data center, space and equipment rented from a recovery provider, or a cloud region. In the cloud, the hot-site equivalent is a full production copy running in a second region.
Example: what a hot site buys
An online brokerage sets a recovery time objective of 30 minutes for its trading platform, because every hour offline means lost trades and regulatory attention. Restoring from backups would take most of a day, so the firm runs a hot site in another region with asynchronous database replication and identical application servers. When a cooling failure forces the primary data center offline, the on-call manager declares a disaster, DNS records are pointed at the hot site, and trading resumes in about 20 minutes. The price is a second set of hardware, licenses, circuits and power, plus the staff time to keep both sites identical.
What can go wrong at a hot site
- Drift: a hot site that misses months of configuration changes and patches fails in ways nobody predicted. Changes must be applied to both sites, and failover must be tested.
- Replicated damage: replication copies deleted records, corruption and ransomware encryption as quickly as good data. A hot site shortens downtime but does not protect against bad changes, so versioned and immutable backups are still needed.
- Shared hazards: a hot site 20 miles away may sit in the same hurricane path, flood plain or power grid region as the primary.
- Weaker security: the recovery environment needs the same firewall rules, MFA, logging and patch levels as production; otherwise failover is the moment defenses are thinnest.
- Common-mode failures: if both sites run the same platform on the same update channel, one bad update can take down both.
Hot site vs. warm site vs. cold site
| Site | In place before a disaster | Data | Typical time to operate | Standing cost |
|---|---|---|---|---|
| Hot | Full hardware, software, network and security tools, running | Current through replication | Minutes to hours | Highest |
| Warm | Hardware and connectivity, partly configured | Restored from recent backups | Hours to days | Medium |
| Cold | Space, power, cooling and network connections | None until restored | Days to weeks | Lowest |
These ranges are typical descriptions, not a standard. Contracts and designs vary, and a well-tested warm site can outperform a neglected hot site.
Hot site on the CompTIA Security+ exam
Recovery sites fall under SY0-801 objective 3.4, which covers why systems must be designed to survive failures and recover from them. Wording such as "must resume within an hour", "minimal downtime" or "near-zero downtime" points to a hot site or an active/active design. Watch for cost: if a question asks for the most cost-effective option and the business can tolerate a day or more of downtime, a warm or cold site is the better answer even though a hot site would also work. Also keep the metrics apart. A hot site shortens downtime, which is the recovery time objective (RTO), but how much data is lost, the recovery point objective (RPO), depends on how current the data at the hot site is.