Site Considerations
Recovery site options for disaster recovery including hot sites (immediate failover), warm sites (hours to recover), and cold sites (days to recover). Understanding cost and recovery time trade-offs for DR planning.
Understanding Site Considerations
Disaster recovery sites provide alternative locations to continue operations when the primary site becomes unavailable. The choice between hot, warm, and cold sites balances cost against recovery time requirements.
Site types by recovery time: • Hot site — Immediate failover (minutes) • Warm site — Hours to activate • Cold site — Days to weeks to activate
After Hurricane Katrina in 2005, organizations with hot sites recovered quickly while those with cold sites (or no DR sites) struggled for weeks. Major banks relocated thousands of employees to hot sites within hours, maintaining critical financial operations.
Site selection must align with business requirements—not every organization needs a hot site, but every organization needs some DR plan.
Why This Matters for the Exam
Site considerations are heavily tested on SY0-701 because they directly impact business continuity. Questions cover site type characteristics, cost comparisons, and selection criteria.
Understanding DR sites helps with disaster recovery planning, budget justification, and business impact analysis. Wrong site choice means either wasted money (over-provisioned) or failed recovery (under-provisioned).
The exam tests recognition of site types and appropriate selection scenarios.
Deep Dive
What Is a Hot Site?
A hot site is a fully operational facility that can take over immediately when the primary site fails.
Hot Site Characteristics:
| Aspect | Description |
|---|---|
| Hardware | Fully equipped, running |
| Software | Installed, configured, updated |
| Data | Real-time or near-real-time replication |
| Network | Connected, ready for traffic |
| Recovery time | Minutes to hours |
| Cost | Highest |
Hot Site Architecture:
When to Use Hot Sites:
- •Mission-critical operations
- •Financial transactions
- •Healthcare systems
- •Revenue-generating applications
- •Strict RTO requirements (< 4 hours)
What Is a Warm Site?
A warm site has infrastructure in place but requires some setup time before becoming operational.
Warm Site Characteristics:
| Aspect | Description |
|---|---|
| Hardware | Installed, may not be running |
| Software | May need installation/configuration |
| Data | Restored from recent backups |
| Network | Available, needs configuration |
| Recovery time | Hours to days |
| Cost | Moderate |
Warm Site Architecture:
When to Use Warm Sites:
- •Important but not mission-critical
- •RTO of 4-24 hours acceptable
- •Budget constraints
- •Moderate data loss acceptable
What Is a Cold Site?
A cold site is a facility with basic infrastructure (power, cooling, connectivity) but no equipment installed.
Cold Site Characteristics:
| Aspect | Description |
|---|---|
| Hardware | None installed |
| Software | None installed |
| Data | Must be restored from offsite backup |
| Network | Basic connectivity only |
| Recovery time | Days to weeks |
| Cost | Lowest |
Cold Site Architecture:
When to Use Cold Sites:
- •Non-critical systems
- •Long RTO acceptable (weeks)
- •Lowest budget
- •Rarely used systems
How Do Site Types Compare?
Comprehensive Comparison:
| Factor | Hot Site | Warm Site | Cold Site |
|---|---|---|---|
| Recovery time | Minutes-hours | Hours-days | Days-weeks |
| Cost | $$$ | $$ | $ |
| Hardware ready | Yes | Partially | No |
| Data current | Real-time sync | Recent backup | Offsite backup |
| Testing ease | Easy | Moderate | Difficult |
| Maintenance | High | Moderate | Low |
Cost vs Recovery Trade-off:
Cost ↑
| [Hot Site]
| *
|
| [Warm Site]
| *
|
| [Cold Site]
| *
+--------------------------------→ Recovery Time
Fast SlowWhat About Cloud-Based DR Sites?
Cloud services have changed DR site economics.
Cloud DR Options:
| Pattern | Description | Recovery |
|---|---|---|
| Pilot light | Minimal always-on | Hours |
| Warm standby | Scaled-down running | Minutes-hours |
| Multi-site active | Full active-active | Immediate |
Cloud Advantages:
- •No hardware procurement delay
- •Pay for what you use
- •Rapid scaling
- •Geographic flexibility
Cloud Pilot Light:
Normal: Minimal resources running (DB replicas, DNS) Failover: Scale up compute, switch traffic Cost: Low (only core running) Recovery: Hours
What Factors Drive Site Selection?
Decision Factors:
| Factor | Consideration |
|---|---|
| RTO | How fast must you recover? |
| RPO | How much data loss acceptable? |
| Cost | Budget for DR infrastructure |
| Criticality | Business impact of downtime |
| Compliance | Regulatory requirements |
| Distance | Geographic separation needed |
Decision Matrix:
| If RTO is... | Consider... |
|---|---|
| < 1 hour | Hot site / Active-active |
| 1-24 hours | Warm site / Pilot light |
| 1-7 days | Cold site / Basic backup |
| > 7 days | May not need dedicated site |
How CompTIA Tests This
Example Analysis
Scenario: A regional bank needs a disaster recovery site for their core banking application. Requirements: RTO of 2 hours, RPO of 15 minutes, regulatory requirement for geographic separation, and budget approval for necessary DR investment.
Analysis - Site Selection:
Requirements:
| Requirement | Value | Implication |
|---|---|---|
| RTO | 2 hours | Must be operational quickly |
| RPO | 15 minutes | Near real-time data needed |
| Geographic separation | Required | Different region |
| Budget | Approved | Cost not primary constraint |
Site Type Analysis:
Cold Site:
Recovery time: Days-weeks RPO: Hours-days (backup restoration) ❌ Cannot meet 2-hour RTO ❌ Cannot meet 15-minute RPO Cost: Lowest Verdict: NOT SUITABLE
Warm Site:
Recovery time: 4-24 hours RPO: Hours (backup frequency) ❌ Cannot meet 2-hour RTO ❌ Cannot meet 15-minute RPO Cost: Moderate Verdict: NOT SUITABLE
Hot Site:
Recovery time: Minutes-hours RPO: Minutes (real-time sync) ✓ Meets 2-hour RTO ✓ Meets 15-minute RPO Cost: Highest Verdict: SUITABLE
Recommended Architecture:
[Primary Site - Region A] [Hot Site - Region B]
(100+ miles away)
[Core Banking] ←──sync──→ [Core Banking Replica]
[Database] ←──sync──→ [Database Replica]
[Transaction Log] ←──ship──→ [Transaction Log]
Synchronous replication for critical data
Asynchronous for bulk data
Automatic failover capabilityImplementation Details:
| Component | Primary | DR Site |
|---|---|---|
| Application servers | Active | Hot standby |
| Database | Primary | Synchronous replica |
| Network | Active | Ready, DNS failover |
| Data sync | - | < 15 minute lag |
Cost Justification:
Downtime cost: $500,000/hour 2-hour RTO = $1M maximum loss Hot site annual cost: $200,000 ROI: Single avoided incident pays for years of DR
Key insight: For banking with strict RTO/RPO requirements, only a hot site can meet recovery objectives. Regulatory compliance also often requires immediate failover capability. The higher cost is justified by downtime costs and compliance requirements.
Key Terms
Common Mistakes
Exam Tips
Memory Trick
Site Temperature = Readiness:
"Hot = Heated up, running now" 🔥 Fully operational, immediate failover
"Warm = Waiting, needs warmup" 🌡️ Equipment there, needs activation
"Cold = Completely empty" ❄️ Just a building, need everything
Recovery Time Memory: "Hot = Minutes, Warm = Hours, Cold = Days" Or: "MHD" = Minutes, Hours, Days
Cost Memory: "The hotter, the higher" (cost) Hot $$$ > Warm $$ > Cold $
Selection Rule: "Match temperature to tolerance" - Can't tolerate ANY downtime? → Hot - Can tolerate HOURS? → Warm - Can tolerate DAYS? → Cold
Geographic Rule: "Far enough to survive, close enough to manage" Different region, same time zone ideal
Test Your Knowledge
Q1.Which recovery site type provides immediate failover capability with real-time data replication?
Q2.A company has an RTO of 48 hours and limited DR budget. Which site type is MOST appropriate?
Q3.What is the PRIMARY trade-off between hot sites and cold sites?
Want more practice with instant AI feedback?
Continue Learning
Ready for the Exam?
See exactly where you stand on this concept and 182 others.
99% pass rate · Pass guarantee