What happens when a server failure brings your entire company to a standstill? That is the problem disaster recovery and business continuity planning solve. For the Server+ exam (SK0-005), you need to know how IT professionals keep systems running when disaster strikes, using metrics like RTO and RPO, and technologies like clustering and high availability.
Jump to a section
A simple way to picture Disaster Recovery and Business Continuity Planning
When the main caterer's kitchen catches fire minutes before the wedding reception, the backup catering truck must be deployed immediately. This situation mirrors disaster recovery and business continuity planning in IT. The bride and groom (the business) need to keep the wedding running despite the crisis. The backup catering truck holds pre-prepared dishes that can be served quickly – this is like disaster recovery, where you restore IT services from backups or failover systems. But the wedding itself doesn’t stop: the couple has a backup menu and cold dishes ready, and the venue has a separate kitchen that wasn’t affected – this is business continuity, where the overall operation continues even if one part fails. The recovery time objective (RTO) is how long guests wait before food arrives, and the recovery point objective (RPO) is how many courses you lose (how much data you can afford to lose). If the main caterer’s fire destroys all hot food, the backup truck only has cold appetisers, so you lose the main course – that’s your RPO. If the backup truck takes 30 minutes to set up, that’s your RTO. The couple’s careful planning – choosing a backup caterer, selecting a venue with two kitchens, and rehearsing the emergency menu – is exactly how IT professionals design a disaster recovery plan and a business continuity plan for a server failure or a data centre outage.
Disaster recovery (DR) and business continuity planning (BCP) are two closely related but distinct concepts. Disaster recovery focuses specifically on restoring IT systems, data, and infrastructure after a disaster. Business continuity is broader – it covers the entire organisation, including people, processes, and facilities, to ensure the business can keep operating during and after a crisis. Both rely on careful planning, defined metrics, and technical solutions.
Let’s start with the key metrics you must know for SK0-005: RTO (Recovery Time Objective) and RPO (Recovery Point Objective). RTO is the maximum acceptable time that a system can be down after a disaster. For example, if your company says the website must be back online within 4 hours, your RTO is 4 hours. RPO is the maximum acceptable amount of data loss, measured in time. If you back up every 1 hour, your RPO is 1 hour – you can afford to lose at most 1 hour of data. These two metrics drive every decision in DR planning.
There are several types of disasters that DR plans must address:
Natural disasters: floods, earthquakes, fires, hurricanes, storms.
Human-caused disasters: accidental deletion, malicious attacks (ransomware), sabotage, vandalism.
Technical failures: hardware failure (e.g., hard drive crash), power outage, network outage, software bugs.
A DR plan typically includes backup strategies and recovery sites. Backup types:
Full backup: copies everything; takes longest, uses most space, but quickest to restore.
Incremental backup: copies only data changed since the last backup (full or incremental); fast backup, but restore requires all incremental backups since the last full backup.
Differential backup: copies data changed since the last full backup; backup is slower than incremental but restore is faster (only need the last full and the latest differential).
Recovery sites are physical locations where you can restore operations if your primary site is destroyed:
Hot site: fully equipped with hardware, software, and real-time data replication. Can take over in minutes or seconds. Most expensive.
Warm site: has some equipment and infrastructure but may need to install and configure software, and data may be a few hours old. Medium cost.
Cold site: just an empty space with power, cooling, and network connections. You bring in all equipment and data. Cheapest but slowest to activate.
High availability (HA) is a design approach that minimises downtime by eliminating single points of failure. Common HA techniques:
Clustering: grouping two or more servers to act as a single system. If one server fails, another takes over (failover). Clustering can be active-active (all nodes handle traffic) or active-passive (one node is standby).
Load balancing: distributing traffic across multiple servers to prevent overload. If one server fails, the load balancer sends traffic to the remaining servers.
Redundancy: duplicate components such as power supplies, network interfaces, hard drives (RAID), and even entire servers.
Why do these exist? Before modern HA and DR, a server failure meant hours or days of downtime while IT staff found replacement parts, restored from tape backups, and reconfigured systems. Today, businesses cannot afford that – e-commerce sites lose revenue every minute, hospitals need patient records available 24/7, and banks must maintain transaction processing. DR and BCP ensure that even when something goes wrong, the impact is contained and recovery is predictable.
Risk Assessment
Identify all potential disasters that could affect the business, such as floods, fires, power outages, cyber attacks, or hardware failures. This step determines what you are planning against.
Business Impact Analysis (BIA)
Analyse which business functions and IT systems are most critical. Determine the acceptable downtime and data loss for each system. This produces the RTO and RPO values that will guide the rest of the plan.
Define RTO and RPO
Set specific, measurable targets for each critical system. For example, the payment processing system must have an RTO of 5 minutes and an RPO of 30 seconds. These numbers drive the choice of recovery strategies.
Design Recovery Strategies
Select the appropriate backup methods (full, incremental, differential), choose a recovery site type (hot, warm, cold), and implement clustering or load balancing. Document the exact steps to failover and restore.
Implement and Document the Plan
Put the strategies into action: set up hardware, configure replication, write runbooks, and assign responsibilities. The plan must include contact details, escalation procedures, and step-by-step instructions.
Test the Plan
Conduct regular tests (tabletop exercises, simulations, or full failover drills) to ensure the plan works and that staff know their roles. Update the plan based on test results and any changes in the environment.
Consider a growing e-commerce company that sells products online. They have a primary server room in their headquarters and a second data centre across town. The IT manager has defined an RTO of 2 hours and an RPO of 15 minutes. This means the website must be restored within 2 hours, and no more than 15 minutes of orders can be lost.
One night, a power surge fries the power supply unit of the main web server. The server shuts down, and customers cannot access the site. The monitoring system immediately alerts the on-call technician.
Step-by-step, what does the IT professional do? - Check the alert and confirm the server is down. The technician logs into the remote management console and sees the server is unresponsive. They quickly determine that the power supply is dead. - Activate the disaster recovery plan. The DR plan document lists the steps for failing over to the secondary data centre. The technician opens the failover script that synchronises the latest database replication (the RPO is 15 minutes, so replication runs every 10 minutes). They verify that the secondary server has the most recent data – only 6 minutes old, well within the RPO. - Perform the failover. The load balancer is reconfigured to direct all traffic to the secondary IP address. Because the secondary server is a hot site with identical hardware and software, it starts accepting requests immediately. The entire failover process takes 7 minutes – far under the 2-hour RTO. - Test the service. The technician loads the website on their own device, places a test order, and confirms that the checkout process works. They also verify that the database shows recent transactions. - Notify stakeholders. The technician sends a brief update to the IT manager and the business continuity team: ‘Failover successful, website operational, RTO and RPO met.’ The business continuity team then communicates to customer support that any issues should be minimal. - Repair the primary server. Meanwhile, another team member replaces the failed power supply and performs a full system check. Once the primary server is stable, they reverse the failover to bring it back as the active server. The secondary server remains as standby. - Update documentation. The technician logs the incident, the time to failover, and any lessons learned. This helps improve the DR plan for future incidents.
In this real-world scenario, the combination of a hot site, automated replication, and a tested failover procedure meant the business never experienced more than a few minutes of downtime. Without these preparations, the e-commerce company could have lost thousands of pounds in sales and damaged its reputation.
The SK0-005 exam tests your understanding of disaster recovery and business continuity planning in several ways. You will see scenario-based multiple-choice questions where you must identify the correct metric, site type, or HA technique. Here is what you need to know:
RTO vs RPO: This is the most common trap. They might give a scenario where a company can tolerate 2 hours of downtime and lose up to 30 minutes of data. You must identify that RTO is 2 hours and RPO is 30 minutes. Traps often reverse the definitions – remember: RTO is time to recover, RPO is data loss (point in time).
Recovery site types: Be clear on hot, warm, and cold sites. The exam may ask which site is most appropriate given a specific budget and RTO. For a short RTO (minutes), hot site is required. For a low budget and longer RTO, cold site might be acceptable. Warm site is in between.
Clustering types: Know the difference between active-active and active-passive. Active-active: all nodes serve traffic; if one fails, remaining nodes handle the load (capacity may degrade). Active-passive: one node is active, one is standby; failover takes a moment but no performance hit during normal operation.
High availability vs fault tolerance: HA reduces but does not eliminate downtime; fault tolerance (e.g., redundant components) can maintain operations even during a failure with zero downtime. The exam may ask which approach allows a system to continue operating without interruption.
Business continuity vs disaster recovery: The exam may ask which is broader. BCP includes DR but also covers alternate work locations, emergency communication, and non-IT processes. DR is only about IT recovery.
Backup strategies: Questions about full, incremental, differential. They may ask which backup type requires the most time to restore (incremental, because you need the full plus all incrementals). Or which uses the least backup media (incremental).
Testing: The exam emphasises that DR plans must be tested regularly. A plan that is never tested is unreliable. You may be asked what type of test is most thorough (simulation or full rehearsal).
Load balancing: Know that load balancers can distribute traffic and also detect server failures to reroute requests. This is part of HA.
Common question patterns: - “A company has an RTO of 1 hour and an RPO of 4 hours. Which recovery site is most cost-effective that meets these requirements?” (Answer: warm site, because it can become operational within an hour and data can be restored from backups that are up to 4 hours old.) - “What is the primary difference between disaster recovery and business continuity?” (Answer: DR focuses on IT systems; BC covers the entire organisation.) - “Which clustering configuration provides automatic failover without manual intervention?” (Answer: both active-active and active-passive can be automated, but typically active-passive is simpler for auto-failover.)
Memorise these definitions:
RTO: maximum downtime allowed.
RPO: maximum data loss allowed (in time).
Hot site: immediate takeover, high cost.
Cold site: slow takeover, low cost.
Active-active clustering: all nodes active.
Active-passive clustering: one node active, one standby.
Recovery Time Objective (RTO) is the maximum acceptable downtime after a disaster, measured in time such as hours or minutes.
Recovery Point Objective (RPO) is the maximum acceptable data loss, also measured in time, such as the age of the last backup.
A hot site provides nearly instant failover but is expensive; a cold site is cheap but requires hours or days to become operational.
Clustering can be active-active (all servers active) or active-passive (one server on standby for failover).
Business continuity planning (BCP) covers the entire organisation including IT, while disaster recovery (DR) focuses solely on restoring IT systems.
Regular testing of a disaster recovery plan is essential – an untested plan is often useless when a real disaster occurs.
Full backups take the longest to create but are the quickest to restore; incremental backups are the opposite.
These come up on the exam all the time. Here's how to tell them apart.
Disaster Recovery
Focuses only on IT systems and infrastructure
Goal is to restore data and services after a disaster
Does not include alternate work locations or staff logistics
Business Continuity
Covers the entire organisation including IT, facilities, and personnel
Goal is to keep the business running during and after a disaster
Includes plans for remote work, communication, and temporary facilities
Hot Site
Fully equipped with hardware, software, and real-time data
Takeover can happen in minutes or seconds
Very expensive to maintain
Cold Site
Empty space with only power and network connectivity
Requires days or weeks to set up and restore data
Cheapest recovery site option
RTO
Maximum downtime allowed after a disaster
Measured in time (e.g., 4 hours)
Drives choice of recovery site and failover technology
RPO
Maximum data loss allowed, measured by age of last backup
Measured in time (e.g., 1 hour)
Drives choice of backup frequency and replication method
Active-Active Clustering
All nodes actively serve traffic simultaneously
If one node fails, remaining nodes handle full load (capacity may degrade)
Better resource utilisation but more complex to configure
Active-Passive Clustering
Only one node is active; one or more are on standby
Failover is automatic but takes a moment; standby node is idle normally
Simpler to manage and predictable performance during normal operation
Full Backup
Copies all data every time
Takes longest to create and requires most storage space
Fastest to restore (only one backup set needed)
Incremental Backup
Copies only data changed since last backup of any type
Fastest to create and uses least storage
Slowest to restore (need full backup plus all incrementals)
High Availability
Designed to minimise downtime but allows brief interruption
Uses redundancy and failover to reduce but not eliminate downtime
Example: clustered servers with automatic failover
Fault Tolerance
Designed to operate through a failure without any interruption
Uses fully redundant components that keep the system running even if one fails
Example: RAID 1 mirrored drives or dual power supplies with automatic switchover
Mistake
Disaster recovery and business continuity are the same thing.
Correct
Disaster recovery is a subset of business continuity. DR focuses on restoring IT systems; BC includes all business functions such as personnel, facilities, and communication.
The terms are used interchangeably in casual conversation, but the exam distinguishes them clearly.
Mistake
A cold site is the cheapest option, so it is always the best choice for small businesses.
Correct
A cold site is cheapest but takes the longest to become operational. If the business cannot afford hours or days of downtime, a warm or hot site is necessary.
Beginners often focus on cost alone, ignoring the RTO and RPO requirements.
Mistake
RPO stands for Recovery Time Objective and RTO stands for Recovery Point Objective.
Correct
It is the opposite: RTO is Recovery Time Objective (time to restore service), and RPO is Recovery Point Objective (maximum data loss measured in time).
The acronyms are easily confused because both start with R and involve 'recovery'. Many students reverse them.
Mistake
High availability means the system never goes down (100% uptime).
Correct
High availability reduces downtime significantly but does not eliminate it. Achieving true zero downtime requires fault tolerance, which is even more expensive and complex.
Marketing claims of 'five nines' (99.999% uptime) are often mistaken for absolute zero downtime.
Mistake
Incremental backups are faster to restore than differential backups.
Correct
Incremental backups are faster to create but slower to restore because you need the full backup and every subsequent incremental. Differential backups require only the full backup and the latest differential, making restoration faster.
Beginners focus on the backup speed advantage of incremental and assume it carries over to restore speed.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
RTO (Recovery Time Objective) is the maximum time allowed to restore a service after a disaster. RPO (Recovery Point Objective) is the maximum amount of data loss you can tolerate, measured by how far back in time your last backup was.
It depends on your budget and RTO. A hot site is better if you need nearly instant recovery; a cold site is cheaper but may take hours or days to become operational. Choose based on your business requirements.
Yes, because disaster recovery only covers IT system restoration. Business continuity covers the whole organisation – including people, alternative work locations, and communication – so your business can keep operating even if IT is down.
Clustering joins two or more servers so they appear as one system. If one server fails, another automatically takes over its workload (failover), reducing downtime.
At least once a year, but more frequent testing is recommended for critical systems. After any major change (like a new application or hardware upgrade), the plan should be re-tested.
High availability minimises downtime but does not guarantee zero downtime – there is still a brief interruption during failover. Fault tolerance uses redundant components so the system continues operating even during a failure, with no interruption.
You've finished Disaster Recovery and Business Continuity Planning. Continue through the SK0-005 study guide to build a complete picture of the exam.
Done with this chapter?