Backup & Recovery Methods
Key Takeaways
- The 3-2-1 rule: keep 3 copies of data, on 2 different media types, with 1 copy off-site or in the cloud — CompTIA's expected baseline backup strategy.
- Full backups clear the archive bit and copy everything; incremental copies (and clears) only changes since the last backup of any type; differential copies changes since the last full and does NOT clear the archive bit.
- Restore math: full + incrementals needs the full plus EVERY incremental since it; full + differential needs only the full plus the single latest differential.
- Recovery Point Objective (RPO) = maximum tolerable data loss in time; Recovery Time Objective (RTO) = maximum tolerable downtime — they are different metrics and CompTIA contrasts them.
- Backups must be tested, and the 220-1202 objective stresses backup verification (test restores) plus the distinction between synthetic full backups and frequent grandfather-father-son rotations.
Backup Types and the Archive Bit
CompTIA A+ objective 4.3 expects you to distinguish three backup types by what they copy and by how they treat the archive bit — a file attribute the OS sets when a file changes.
| Type | Copies | Archive Bit | Storage | Restore Speed |
|---|---|---|---|---|
| Full | Everything | Cleared | Most | Fastest (1 set) |
| Incremental | Changes since the last backup of any type | Cleared | Least | Slowest (full + every incremental) |
| Differential | Changes since the last full | NOT cleared | Medium | Medium (full + latest differential only) |
Because a differential never clears the archive bit, each day's differential keeps growing until the next full, but you only ever need two sets to restore. An incremental clears the bit, so each one is small and fast to create, but restoring requires the full plus every incremental in sequence.
Restore Math (Heavily Tested)
This is the most common Domain 4 calculation question.
Full (Sunday) + daily incrementals — restore Thursday:
| Sets needed | Sun full | Mon inc | Tue inc | Wed inc | Thu inc |
|---|---|---|---|---|---|
| 5 total | yes | yes | yes | yes | yes |
Full (Sunday) + daily differentials — restore Thursday:
| Sets needed | Sun full | Thu differential |
|---|---|---|
| 2 total | yes | yes |
Rule of thumb: Incremental = fast backup, slow restore. Differential = slower backup each day, fast restore. Pick incremental when storage/backup window is tight; differential when fast recovery matters more.
The 3-2-1 Rule
| Digit | Meaning | Example |
|---|---|---|
| 3 | copies of the data | Original + 2 backups |
| 2 | different media types | Internal SSD + external HDD |
| 1 | copy off-site/cloud | Backblaze or a second building |
This protects against single-drive failure, site-level disasters (fire, theft, flood), and ransomware that encrypts everything reachable on the LAN.
Recovery Objectives: RPO vs RTO
| Metric | Question It Answers | Example |
|---|---|---|
| RPO (Recovery Point Objective) | How much data can we afford to lose? | 4-hour RPO = back up at least every 4 hours |
| RTO (Recovery Time Objective) | How long can we be down? | 2-hour RTO = restored within 2 hours |
A tight RPO drives backup frequency; a tight RTO drives restore speed (which favors full or differential, and image-based recovery). The exam pairs each definition with one metric — do not swap them.
Backup Verification and Rotation
A backup you cannot restore is worthless, so CompTIA stresses backup testing/verification: periodically perform a test restore to confirm the media and job are good. Common rotation schemes:
- Grandfather-Father-Son (GFS) — daily (son), weekly (father), monthly (grandfather) sets, balancing retention with media use.
- 3-2-1 — the storage-distribution baseline above.
- On-site vs off-site/cloud — on-site restores fast; off-site/cloud survives a site disaster but restore speed depends on bandwidth.
Worked example: A small office has a 1-hour RTO and a 24-hour RPO. A nightly full backup satisfies the 24-hour RPO, and keeping that full on a fast local NAS plus a cloud copy satisfies the 1-hour RTO for local failures and the off-site requirement of 3-2-1. Switching to nightly incrementals would shrink the backup window but risks blowing the 1-hour RTO during a multi-set restore.
Choosing the Right Strategy on the Exam
CompTIA backup questions reward you for matching a strategy to a constraint. When a scenario emphasizes limited storage or a very short nightly backup window, the intended answer is incremental, because each incremental captures only the small set of files changed since the previous backup. When a scenario emphasizes fast or simple recovery, the intended answer is differential, because restoring requires only the most recent full plus the single latest differential rather than chaining many sets together.
A pure full-only strategy is correct when the data set is small enough to capture completely every night and recovery simplicity is the priority. Watch for distractors that mix the definitions, for example claiming that an incremental backup copies everything since the last full; that description actually belongs to a differential backup, and the swap is the single most common trick in this objective.
Backup Media, Location, and Why Testing Matters
The exam also distinguishes where backups live and how that affects both safety and recovery speed. An on-site backup on a local network-attached storage device restores quickly but shares the fate of the building in a fire, flood, or theft. An off-site or cloud backup survives a site-level disaster and is the copy that satisfies the off-site leg of the 3-2-1 rule, but its restore speed is gated by available internet bandwidth, which is why a large cloud-only restore can blow an aggressive recovery time objective.
This trade-off is why mature plans keep a fast local copy for routine restores and a cloud copy for disaster recovery rather than relying on either alone.
Finally, never lose sight of verification. A backup job that reports success but produces unrestorable media gives a false sense of safety, and CompTIA repeatedly frames this as the reason regular test restores are mandatory. A test restore confirms that the media is readable, the job captured the intended data, and the documented recovery steps actually work under pressure.
Encrypting backups, especially off-site and cloud copies, protects the data at rest, and documenting exactly what is backed up, how often, and how to restore it turns the backup plan into something any technician on the team can execute during an outage rather than tribal knowledge held by one person.
Which backup type copies all changes made since the last FULL backup and does not clear the archive bit?
Using a Sunday full backup plus daily incrementals, how many backup sets are required to restore data from Wednesday?
A backup design must guarantee the system is operational within two hours of a failure. Which recovery metric does that two-hour target define?
Which statement best captures the 3-2-1 backup rule?