HealthITPrep
CPHIMS guide Concepts Features Pricing FAQ
Sign in Start free
العربية

Full vs differential vs incremental backup, with RTO and RPO

By Adel Moustafa, CPHIMS® · Updated 22 October 2026

The three types of backup, what each needs for a restore, the two targets that decide how often to back up and how fast to recover, and where the disaster recovery plan fits.

In short: a full backup copies everything. An incremental backup copies only what changed since the last backup of any kind, so a restore needs the last full backup and every incremental after it. A differential backup copies everything changed since the last full backup, so a restore needs only the last full and the latest differential. The RPO says how much data, in time, the organisation can afford to lose; the RTO says how long the service may be down.
The three types What a restore needs Side by side RPO and RTO BCP and DRP Recovery sites Common mistakes Summary Sources

What are the three types of backup?

  • Full: a copy of all the selected data, every time. The simplest to restore, but the slowest to make and the largest to store.
  • Incremental: only the data that changed since the last backup of any type, full or incremental. Each one is small and quick to make.
  • Differential: all the data that changed since the last full backup. Each day's differential is usually larger than the day before, until the next full backup starts the count again.

Most organisations combine them: a full backup once a week, for example, and incremental or differential backups on the other nights.

Which backups does a restore need?

Take a full backup every Sunday night, and a failure on Thursday morning, with the data to be brought back to its state on Wednesday night.

  • With differential backups on the other nights: Sunday's full backup and Wednesday's differential only. Wednesday's differential already holds every change since Sunday.
  • With incremental backups: Sunday's full backup and the Monday, Tuesday and Wednesday incrementals, applied in that order. If one of them is missing or damaged, the changes after it cannot be restored correctly.

So the trade-off is simple: incremental backups are faster to make and restore more slowly; differential backups take longer to make each day and restore faster.

Full, differential and incremental side by side

FullDifferentialIncremental
What it copiesEverything selectedChanges since the last fullChanges since the last backup of any type
Time and space to make itThe mostGrows each day after the fullThe least
What a restore needsThat one backupThe last full and the latest differentialThe last full and every incremental after it, in order
Speed of restoreFastestFastSlowest

What are RPO and RTO?

  • Recovery point objective (RPO): the most data the organisation can accept to lose, measured in time. An RPO of 4 hours means that after a failure, the data may go back no more than 4 hours. It decides how often to back up or replicate: nightly backups cannot meet a 4-hour RPO.
  • Recovery time objective (RTO): the longest the system may stay unavailable before it must be working again. It decides how to recover: restoring from tape in another city may take a day; failing over to a standby system may take minutes.
  • Both come from the business impact analysis (BIA), which asks each department what a lost hour of each system costs, for patients and for the organisation. The BIA also gives the maximum tolerable downtime, the outer limit; the RTO must not exceed it.

The tighter the targets, the higher the cost. An RPO and RTO close to zero mean real-time replication to a second site, which is why they are set system by system: the EHR and the pharmacy system usually get far tighter targets than an archive of old scanned documents.

How do the business continuity plan and the disaster recovery plan differ?

  • Business continuity plan (BCP): how the organisation keeps its critical functions running during and after a disruption: people, processes, places and communication. In a hospital that includes downtime procedures, such as paper order forms, a read-only copy of recent patient data, and the steps to enter the paper records once the system returns.
  • Disaster recovery plan (DRP): the technical part, how IT restores systems, data and infrastructure after a disaster. The DRP supports the BCP: it brings the systems back, and the BCP keeps care going until they are back and afterwards. NIST treats them as separate plans that work together; many textbooks describe the DRP as part of the BCP.

Both must be tested. Tests range from a walk-through of the plan around a table, through a simulation and a parallel test on the recovery site, to a full interruption test, the most realistic and the most disruptive. The HIPAA Security Rule requires a contingency plan with a data backup plan, a disaster recovery plan and an emergency mode operation plan; testing and revising the plan, and an analysis of which applications and data are most critical, are addressable.

What are hot, warm and cold recovery sites?

  • Hot site: a second site with systems running and data kept current, ready in minutes or hours. The most expensive.
  • Warm site: some equipment and connections in place; systems must be loaded and data restored. Ready in hours to days.
  • Cold site: space, power and cooling only. Equipment must be brought and installed. Days to weeks, and the cheapest.

Cloud services now often play the role of the warm or hot site. The choice follows the RTO: a system with an RTO of one hour cannot depend on a cold site.

What do candidates get wrong?

  • Swapping incremental and differential. Differential: since the last full. Incremental: since the last backup of any type.
  • Adding every differential to the restore. Only the latest differential is needed, with the last full.
  • Swapping RPO and RTO. RPO is about data (how far back), RTO about time (how long down).
  • Treating replication as a backup. A mirror copies a deletion, a corruption or ransomware encryption to the second site at once. A backup that can go back in time, ideally offline or unchangeable, is still needed. A common rule of practice is 3-2-1: three copies, on two kinds of media, one of them off site.
  • Calling the DRP the whole plan. The DRP is the technical plan that supports the BCP; downtime procedures for clinicians belong to the BCP.
  • Never testing a restore. A backup that has never been restored is an assumption, not a plan.

Summary for revision

  • Full: everything; one backup restores.
  • Differential: since the last full; restore = last full + latest differential.
  • Incremental: since the last backup; restore = last full + every incremental after it.
  • RPO = how much data may be lost (backup frequency); RTO = how long the system may be down (recovery method). Both come from the BIA.
  • The DRP supports the BCP; hot, warm and cold sites follow the RTO.

Sources

  • NIST Special Publication 800-34 Revision 1, Contingency Planning Guide for Federal Information Systems: business impact analysis, RTO, RPO, maximum tolerable downtime, backup and alternate sites, testing.
  • HIPAA Security Rule, 45 CFR 164.308(a)(7): contingency plan (data backup, disaster recovery, emergency mode operation, testing and revision).

Related free practice questions

  • Types of backup: full, differential and incremental
  • The continuity plan contains the disaster recovery plan

The site files this concept under the domain Healthcare and Technology Environments.

Try exam-style questions

A 20-question trial exam with an explanation for every option and a score per domain, drawn from 40 free questions. No payment method needed.

Start the trial exam

Questions about the exam: CPHIMS guide · What is CPHIMS? · Exam cost · Eligibility · Passing score · Renewal · Exam day · How long to study · Is it worth it? · What is CAHIMS?

Concepts explained: HL7 v2 vs FHIR · Capitation vs fee-for-service · Safe Harbor vs Expert Determination · Incident vs problem vs change · Privacy Rule vs Security Rule · CDS five rights · Lewin vs Kotter · SDLC and go-live strategies · Testing types · Earned value (SPI, CPI) · Structure, process, outcome · HIE models · Six Sigma vs Lean · Levels of interoperability · Bandwidth vs latency · EMTALA · Risk responses · RACI matrix · Build vs buy · Sunk vs opportunity cost · Data governance

The four domains: Healthcare and Technology Environments · Clinical Informatics · Healthcare Information and Systems Management · Management and Leadership

Written by Adel Moustafa, About us

Written and checked against the sources above on 22 October 2026. An independent site, not affiliated with or endorsed by HIMSS. CPHIMS® is a registered trademark of HIMSS.

CPHIMS guide Compare certifications Free practice questions Concepts explained About us Terms of Use Privacy Policy Refund Policy Contact us

© 2026 HealthITPrep. This site is not affiliated with or endorsed by HIMSS. CPHIMS is a registered trademark of HIMSS.