For CompTIA A+ Core 2 (220-1202), Domain 4.0 (Operating Systems), Objective 4.3 (Backup), you're expected to know more than a definition. You need to pick a backup method that fits real limits, like slow Wi-Fi, tight storage, and a short maintenance window. Backups also show up in real support work, because users don't call when things go well. They call after a bad update, a spilled coffee, or a ransomware popup. This article breaks down four backup types you must know (full, incremental, differential, synthetic full) and explains what each one costs you in time, storage, and restore effort. Those differences matter, because the "best" plan changes based on what you protect and how fast you must recover.
What a backup really is, and what it protects you from
A backup is a separate copy of data that you can restore later. That sounds simple, yet the word "copy" hides the most important detail: a backup has to survive the same disaster that hit the original. If the only copy sits on the same drive, it's not protection, it's just a duplicate.
Most data loss comes from ordinary problems, not rare events. Drives fail after years of heat and vibration. Users delete the wrong folder and then empty the recycle bin. Malware can encrypt files in minutes. A rushed OS update can break profiles or corrupt system files. Theft and loss count too, especially for laptops and tablets used in travel.
In practice, backups protect against both device failure and human error. They also protect against time. A user might not notice a missing file for days, so a good backup plan keeps older versions long enough to matter.
It also helps to separate "backup" from other data tools people treat as backups. Sync tools focus on keeping two locations identical. Archive tools focus on long-term retention and recordkeeping. Backups focus on recovery after a mistake or outage.
Finally, think about recovery as a business decision, even at home. Two ideas guide that decision:
- How much data can you lose? If yesterday's work disappears, is that acceptable?
- How long can you be down? If restore takes a day, what breaks?
Those questions lead straight to RPO and RTO, which show up in many backup discussions because they turn vague worry into clear targets.
Backup, sync, and archive are not the same thing
A backup keeps restore points, so you can roll back to an earlier, known-good state. For example, a nightly backup of a student's Documents folder lets them restore the version from last Tuesday.
Sync keeps folders the same across devices. For example, a cloud sync folder might copy a file from a laptop to a phone within seconds. That's convenient, but it can copy problems too.
Archive stores data for long-term access, often to meet policy or legal needs. For example, a person might archive yearly tax PDFs to external storage and keep them for seven years.
The main risk with treating sync as backup is simple: bad changes replicate. If a user deletes a folder, sync may delete it everywhere. If ransomware encrypts files, sync can upload encrypted versions and overwrite clean ones.
If the tool's job is "make both sides match," it can't tell a mistake from a plan.
Two numbers that guide every backup plan: RPO and RTO
RPO (Recovery Point Objective) is how much data you can afford to lose, measured in time. If your RPO is 24 hours, then a daily backup cadence fits the goal. If your RPO is one hour, daily backups won't meet it.
RTO (Recovery Time Objective) is how fast you need service back. If your RTO is two hours, you need quick restores, clear procedures, and backups that don't require long rebuild steps.
A short story makes this concrete. A student laptop used for homework might have an RPO of one day and an RTO of one day. If the laptop fails, they can restore tomorrow, because the deadline is next week. In contrast, a small office file share might have an RPO of four hours and an RTO of two hours. If staff can't open files, work stops, so both backup frequency and restore speed matter.
In other words, RPO pushes how often you back up, while RTO pushes how you design restores.
The four backup types you must know for Core 2 objective 4.3
Backup types sound like exam terms until you feel their tradeoffs. Some save storage but slow restores. Others restore fast but cost more space and time. The best choice depends on change rate, network limits, and your RPO and RTO targets.
Before the details, keep one memory aid in mind: storage versus restore effort. Full backups use the most space per run but restore in one step. Incrementals save space but can create a long chain. Differentials sit in between.