This objective focuses on Disaster Recovery (DR) and business continuity. It covers the specific math metrics used to measure downtime limits, the types of backup data centers a company can maintain, and how to design high-availability systems so that a hardware failure doesn’t cause a business collapse.
CompTIA tests these concepts strictly from an organizational planning perspective.
1. Disaster Recovery Metrics (The Time and Data Math)
When a disaster strikes (such as a lightning strike, a ransomware attack, or a water leak in the server room), management uses four critical metrics to define its operational targets.
RPO vs. RTO (The Two Big Targets)
- RPO (Recovery Point Objective): This measures how much data you can afford to lose before causing serious harm to the company. It dictates how frequently you must take backups.
- Simple Example: If a bank sets an RPO of 1 hour, it must back up its transaction databases at least once every hour. If the system crashes at 4:00 PM, they must be able to restore the data up to at least 3:00 PM. The maximum amount of data “lost in the fire” is 1 hour’s worth.
- RTO (Recovery Time Objective): The maximum target time for restoring systems to normal operation after an outage. It is your downtime deadline.
- Simple Example: If a company has an RTO of 4 hours, the IT team has exactly 4 hours from the moment the power goes out to get the network back online and users working again before failing the service agreement.
MTTR vs. MTBF (The Equipment Vitals)
- MTTR (Mean Time to Repair): The average time it takes to repair a broken component and restore service. It measures efficiency.
- Simple Example: If a switch fails three times and it takes 30, 60, and 90 minutes to swap it out, the MTTR is 60 minutes.
- MTBF (Mean Time Between Failures): A metric predicting the reliability and lifespan of a piece of hardware. It represents the average time a device is expected to run before it breaks.
- Simple Example: High-end enterprise hard drives might have an MTBF of 1.5 million hours, helping engineers plan proactive hardware replacement cycles.
2. Disaster Recovery Sites (The Backup Locations)
If a natural disaster destroys a main data center, a company must shift operations to a secondary backup facility. There are three tiers of DR sites, balancing cost against speed:
- Cold Site: An empty room or data center space with power, cooling, and physical racks, but no hardware, servers, or data.
- How it works: It is the cheapest option, but it takes days or weeks to go live because you must physically ship servers to the site, install the OS, run cables, and restore old backup tapes.
- Warm Site: A compromise site. It contains physical racks with servers and switches already plugged in, but the servers and switches are turned off or not actively synced.
- How it works: The hardware is ready, but the data is old. To go live, engineers must boot the hardware and download the latest data backups from a cloud storage bucket. Going live usually takes several hours to a couple of days.
- Hot Site: A mirror-image duplicate of your production data center. It has identical hardware running 24/7, with real-time data synchronization.
- How it works: If the main site goes dark, a hot site can take over the entire corporate network load within seconds or minutes, with zero data loss. It is incredibly fast but massively expensive to maintain.
3. High-Availability Approaches (Redundancy Configurations)
To avoid needing to use a disaster recovery site for a simple hardware failure, networks use high-availability (HA) design layouts to keep systems up continuously.
Active-Active
- How it works: Multiple redundant devices (like two firewalls or two load balancers) are online, running simultaneously, and actively sharing the network traffic load equally.
- Advantage: You get maximum performance because both devices are working for you. If one dies, the remaining device continues to run, though performance might drop slightly as it absorbs 100% of the load.
Active-Passive
- How it works: One device handles 100% of the live network traffic (Active), while an identical backup device sits turned on but idle, silently watching the main device (Passive).
- Advantage: If the active device stops responding, the passive device immediately wakes up, inherits the configuration, and automatically takes over the traffic load.
4. Disaster Recovery Testing
Plans are useless unless they are tested. CompTIA highlights two distinct methods for auditing a disaster recovery plan:
- Tabletop Exercises (Theoretical Test): A low-stress, discussion-based classroom meeting. Key stakeholders, managers, and engineers sit around a conference table. At the same time, a coordinator describes a simulated disaster scenario (e.g., “A water pipe burst in the data center. What do you do?”). The team walks through the documentation step by step to identify gaps or outdated contact numbers without touching a single live server.
- Validation Tests (Practical Test): A hands-on, live technical drill. Engineers actually execute the technical disaster recovery plan—such as intentionally severing a main internet trunk link or deploying a server infrastructure from backup images onto separate hardware to verify that the RTO and RPO targets can actually be achieved in the real world.
Disaster Recovery Cheat Sheet for the Exam
| Term / Concept | Focus Metric / Type | Core Identifier / Clue |
| RPO | Data Loss | Maximum age of data that can be lost from backups. |
| RTO | Downtime Goal | Targeted timeline limit to restore a broken service. |
| Hot Site | DR Location | Mirror-image copy; running 24/7 with real-time data sync. |
| Cold Site | DR Location | Empty facility; takes weeks to deploy; cheapest option. |
| Active-Active | High-Availability | Multiple devices are processing live traffic simultaneously. |
| Tabletop | Testing | Verbal discussion in a conference room; no systems altered. |