Overview
Business Continuity covers how a DBA keeps data available and recoverable. Objective 5.1 explains disaster recovery (DR): the documentation that guides it (DR manuals, the system security plan, the continuity of operations plan and build documentation), the techniques that keep a second copy ready (replication, log shipping, high availability and mirroring), testing the plan against the recovery point objective (RPO) and recovery time objective (RTO), and the transition back to normal operations through failback.
Objective 5.2 explains backup and restore: full, incremental and differential backups, database dumps, scheduling and automation, testing restores, validating backup hashes, choosing on-site and off-site storage, and retention cycles that purge or archive. It depends on the monitoring from Domain 3 to notice failed jobs and on the ransomware awareness from Domain 4 to keep at least one copy out of an attacker's reach.
How it's tested
Domain 5 questions are short scenarios with precise answers. You may calculate which backups a restore needs, pick the DR technique that meets a stated RPO and RTO, name the document that guides recovery, or choose the step that proves a backup is usable. Read every time value in the stem carefully.
-
Build the restore chain
A backup schedule and a failure time are given and you choose which backups to restore, in what order, to reach the latest recoverable point.
-
Match technique to target
An RPO and RTO are stated, such as near-zero data loss within minutes, and you choose synchronous replication, mirroring, log shipping or backup-based recovery.
-
Prove recoverability
A backup or DR process is described and you pick the step that validates it, such as a restore test, hash comparison or scheduled DR exercise.
A business says it can lose at most 15 minutes of transactions and must be back online within one hour. Options include nightly full backups to tape, log shipping with 10-minute log backups to a warm standby, weekly differentials, and an annual tabletop exercise. Nightly backups could lose a day of data. Log shipping every 10 minutes keeps loss inside 15 minutes and a warm standby can be brought online within the hour.
Objectives 2
Official objectives from the CompTIA outline, in outline order.
5.1 Explain the importance of disaster recovery and relevant techniques.DR documentation, replication, log shipping, high availability, mirroring, RPO and RTO testing, and failback.
- What it means
- Disaster recovery restores database service after a major failure such as a site outage, hardware loss or destructive attack. The objective covers DR documentation (manuals, the system security plan, the continuity of operations plan and build documentation), the techniques of replication, log shipping, high availability and mirroring, testing the DR plan against RPO and RTO, and transitioning back to normal operations with failback.
- What to understand
- RPO is the maximum acceptable data loss measured in time, so it sets how often data must be copied; RTO is the maximum acceptable downtime, so it sets how fast service must return. Synchronous replication or mirroring can approach zero data loss but adds write latency; asynchronous replication and log shipping accept some loss for less overhead and greater distance. Build documentation lets a team rebuild a server consistently, and a plan only counts once it has been tested.
- How it shows up
- A scenario gives recovery targets, a failure type or a post-incident step and asks for the technique, the document or the next action, including when and how to fail back.
- Common confusion
- Swapping RPO and RTO, or assuming high availability within one data center also covers the loss of that site.
5.2 Explain backup and restore best practices and processes.Full, incremental and differential backups, dumps, scheduling, automation, testing, hash validation, storage location and retention.
- What it means
- A full backup copies everything; an incremental copies changes since the last backup of any type; a differential copies changes since the last full backup. The objective also covers database dumps, scheduling and automating backups, testing them, validating backup hashes, choosing on-site versus off-site storage, and retention with purge and archive cycles.
- What to understand
- Restore effort follows the backup type: full plus every incremental in order, or full plus only the latest differential. A dump is a logical export, such as SQL statements from pg_dump or mysqldump, that is portable across versions but slower to restore for large databases. Hashes taken at backup time and compared later prove a file was not altered or corrupted, but only a test restore proves the backup is usable. Off-site copies survive a site disaster; on-site copies restore faster.
- How it shows up
- A schedule and failure time are given and you choose the restore set, or a requirement such as proving integrity or surviving a fire points to a practice.
- Common confusion
- Reversing incremental and differential, or treating a successful backup job status as proof the backup can be restored.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
RPO
The recovery point objective is the maximum amount of data, measured in time, the business can afford to lose.
- Remember
- RPO drives backup and replication frequency: a 15-minute RPO needs copies at least every 15 minutes.
- Tested as
- Technique-selection and schedule questions.
- Trap
- Treating RPO as how long recovery may take.
-
RTO
The recovery time objective is the maximum time a service may be unavailable before the business impact becomes unacceptable.
- Remember
- RTO drives standby readiness: short RTO needs a warm or hot standby, not a restore from scratch.
- Tested as
- DR technique questions pair RTO with RPO.
- Trap
- Meeting RPO with frequent backups but ignoring how long restoring them would take.
-
Full vs. incremental vs. differential
A full backup copies all data; an incremental copies changes since the last backup of any type; a differential copies changes since the last full backup.
- Remember
- Incremental: small backups, long restore chain. Differential: growing backups, two-step restore.
- Tested as
- Restore-chain calculations.
- Trap
- Restoring every differential instead of just the latest one.
-
Database dump
A dump is a logical backup that exports schema and data as SQL statements or a portable archive.
- Remember
- Dumps are portable and good for migrations or single-object recovery, but slow for very large databases.
- Tested as
- Questions about moving data between versions or platforms.
- Trap
- Assuming a dump is the fastest way to restore a multi-terabyte database.
-
Backup testing
A backup test restores the backup to a separate system and verifies data and application function.
- Remember
- A job that reports success is not proof; only a restore proves recoverability.
- Tested as
- Questions on validating backup processes.
- Trap
- Relying on job success status or file size as evidence.
-
Hash validation
A cryptographic hash such as SHA-256 is recorded when a backup is created and recomputed later; matching values show the file has not changed.
- Remember
- Hashes prove integrity of the file, not that its contents restore correctly.
- Tested as
- Integrity checks for backups moved off-site or stored long term.
- Trap
- Equating a matching hash with a successful restore test.
-
Replication
Replication continuously copies changes from a primary database to one or more secondaries, synchronously or asynchronously.
- Remember
- Synchronous minimizes data loss but adds latency; asynchronous tolerates distance with some loss.
- Tested as
- DR technique selection.
- Trap
- Treating replication as a backup; deletions and corruption replicate too.
-
Log shipping
Log shipping backs up transaction logs on the primary, copies them to a standby server and restores them there on a schedule.
- Remember
- Loss is bounded by the log backup interval; a restore delay can protect against recent logical errors.
- Tested as
- Warm-standby scenarios with minute-level RPO.
- Trap
- Expecting automatic, instant failover from log shipping alone.
-
Mirroring
Mirroring maintains a copy of a database on a second server, kept in step synchronously or asynchronously, ready to take over.
- Remember
- It provides a ready standby copy of a single database; synchronous mode trades latency for no committed-data loss.
- Tested as
- High-availability and DR comparisons.
- Trap
- Assuming a mirror protects against accidental deletes, which are mirrored too.
-
High availability
High availability uses redundancy such as clustering and automatic failover to keep service running through component failures.
- Remember
- HA reduces downtime from local failures; DR covers the loss of a site.
- Tested as
- Distinguishing HA from DR in scenarios.
- Trap
- Treating a single-site cluster as a disaster recovery plan.
-
Continuity of operations plan (COOP)
A COOP describes how essential functions continue during and after a disruption, including roles, alternate sites and priorities.
- Remember
- COOP covers the organization's essential functions; DR documentation covers restoring specific systems.
- Tested as
- Document-selection questions in 5.1.
- Trap
- Using the system build documentation to answer who leads during a disruption.
-
Failback
Failback is the planned return of operations from the DR site or standby to the primary environment once it is repaired.
- Remember
- Resynchronize data changed during the outage before switching back.
- Tested as
- Post-incident sequencing questions.
- Trap
- Switching back immediately and losing transactions written at the DR site.
-
Off-site vs. on-site storage and retention
On-site copies restore fastest; off-site copies survive a site-wide disaster; retention policies decide when copies are purged or moved to archive.
- Remember
- Keep at least one copy off-site and, for ransomware, offline or immutable.
- Tested as
- Storage-location and retention scenarios.
- Trap
- Keeping every copy in the same building as the server.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
RPO vs. RTO
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| RPO | Maximum acceptable data loss, measured back from the failure | Sets how often data is copied | Reading it as allowed downtime |
| RTO | Maximum acceptable downtime after the failure | Sets how ready the standby must be | Meeting it on paper with backups that take hours to restore |
Full vs. incremental vs. differential backup
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Full | Copies all data | Slowest to take, simplest to restore | Running only fulls when the backup window cannot fit them |
| Incremental | Changes since the last backup of any type | Smallest daily backups; restore needs full plus every incremental in order | Missing one link breaks the chain |
| Differential | Changes since the last full backup | Grows daily; restore needs full plus the latest differential only | Restoring every differential in sequence |
Replication vs. log shipping vs. mirroring vs. backups
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Replication | Continuous copy of changes to secondaries | Near-real-time copies; can feed read replicas | Treating it as protection against deletion or corruption |
| Log shipping | Scheduled log backups restored on a standby | Minute-level RPO; optional restore delay | Expecting automatic instant failover |
| Mirroring | Second copy of a database kept in step | Ready standby; synchronous mode avoids committed-data loss | Assuming it undoes logical errors |
| Backups | Point-in-time copies stored separately | Recover to earlier points and from ransomware if kept offline | Assuming they meet a short RTO without a standby |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Replication is a backup
- What candidates pick
- Rely on a replica as the organization's backup.
- Why it looks right
- The replica is a complete second copy of the data.
- Why it's wrong
- Replication copies deletes, corruption and ransomware encryption to the secondary, so there is no earlier point to return to.
Clue to watch for Recovering from an accidental delete, corruption or malware rather than hardware loss.
-
Every differential
- What candidates pick
- Restore the full backup, then each differential from every day since.
- Why it looks right
- It feels thorough, like replaying incrementals.
- Why it's wrong
- Each differential already contains all changes since the full, so only the latest is needed; restoring all wastes time against the RTO.
Clue to watch for The schedule says differential, not incremental.
-
RPO as downtime
- What candidates pick
- Choose a technique that brings the service back in 15 minutes when the RPO is 15 minutes.
- Why it looks right
- Both targets are expressed in minutes.
- Why it's wrong
- RPO limits data loss, not downtime; the technique must copy data at least every 15 minutes, and RTO is a separate requirement.
Clue to watch for Look for which target the stem names and whether it describes lost data or lost service time.
-
Green job equals good backup
- What candidates pick
- Treat a backup job's success status as proof of recoverability.
- Why it looks right
- Monitoring shows no failures.
- Why it's wrong
- Jobs can succeed while writing incomplete or unusable files; only a periodic test restore, with hash checks for integrity, proves recovery works.
Clue to watch for Requirements to verify, prove or validate backups.
-
HA as DR
- What candidates pick
- Use a two-node cluster in the same data center as the disaster recovery plan.
- Why it looks right
- It provides automatic failover and high uptime.
- Why it's wrong
- A site-wide event such as fire, flood or power loss takes out both nodes; DR needs a copy at a separate location.
Clue to watch for The scenario mentions site loss, regional outage or natural disaster.
-
Immediate failback
- What candidates pick
- Switch users back to the primary as soon as it powers on.
- Why it looks right
- Normal operations are the goal.
- Why it's wrong
- Transactions written at the DR site must be resynchronized first, and the primary must be validated, or data is lost or split.
Clue to watch for The stem describes returning after an outage during which the standby accepted writes.
Answer framework
Use this sequence when a Domain 5 question asks you to plan, choose or validate a recovery approach.
- Write down the RPO and RTO from the stem and note which describes data loss and which describes downtime.
- Identify the failure type: component failure, site loss, logical error such as an accidental delete, or malware such as ransomware.
- Choose the technique that meets both targets for that failure type, such as synchronous replication or mirroring for near-zero loss, log shipping for minute-level loss, or offline backups for logical damage.
- For restores, build the chain from the backup types: full plus all incrementals in order, or full plus the latest differential, then apply logs if available.
- Confirm the plan is proven by restore tests, hash validation, off-site copies and scheduled DR exercises, and plan the failback.
Practice question
Want more like this? The CompTIA DataSys+ practice test has questions for every domain.
Checklist
0 of 13
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Start with RPO and RTO, because almost every question in objective 5.1 turns on them. Write both definitions in one line each, then practice turning business statements such as no more than an hour of lost orders into the correct target. Next, build a table of replication, log shipping, mirroring, high availability and backups showing typical data loss, recovery speed, distance and what each fails to protect against.
For objective 5.2, draw a week of backups on paper with full, incremental and differential combinations and work out the restore set for failures on different days until it is automatic. Then on a practice instance take a full and a differential backup or a dump, record a SHA-256 hash, restore to a new database and compare row counts and checksums.
Candidates commonly underestimate the documentation list in 5.1 and the failback step. Learn what the continuity of operations plan, the system security plan and build documentation each contain, and why data written at the DR site must be synchronized before switching back.
Afterward, take timed practice sets mixing restore-chain and technique questions, then review the whole exam with a full-length mock.
FAQ
How much of DataSys+ DS0-001 is Business Continuity?
CompTIA weights it at 12%, the smallest domain, across two objectives. CompTIA does not publish per-domain question counts, so any number for this domain is an estimate.
What is the difference between RPO and RTO?
RPO is how much data, measured in time, the business can afford to lose; RTO is how long the service can be down. RPO drives copy frequency and RTO drives standby readiness.
How do incremental and differential backups differ when restoring?
With incrementals you restore the full backup and then every incremental in order. With differentials you restore the full backup and only the most recent differential.
Is replication enough for disaster recovery?
Replication helps meet short RPO and RTO for hardware or site failures, but it copies deletions, corruption and ransomware encryption. Backups kept separately, including offline or immutable copies, are still required.
Will I need to calculate restore sequences?
The objectives name full, incremental and differential backups, and scenario questions commonly ask which backups are needed after a failure. Practicing restore chains on paper is a reliable way to prepare.
Is a small domain worth deep study?
Yes. Its questions are precise and predictable, so time spent on RPO, RTO, restore chains and DR techniques converts directly into points, and it reinforces monitoring and ransomware topics from other domains.
How does Domain 5 relate to the others?
It depends on Domain 3 to monitor backup and replication jobs, on Domain 4 to understand threats such as ransomware, and on Domain 2 for the architecture and build documentation used to rebuild servers.
Other Data & Analytics certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 5 knowledge
You have just worked through RPO and RTO, DR techniques, restore chains and backup validation. Check whether you can build the right restore set and pick the right technique when the numbers are in the stem.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the CompTIA DataSys+ AI tutor Get any concept explained your way