A topic in the Open Knowledge Graph — a free, open map of 15,290 topics and the order to learn them in.
System backup goes beyond saving individual files — it captures the entire state of your operating system, installed programs, settings, and data so that a failed hard drive, ransomware attack, or corrupted update does not mean starting from scratch. System restore points save snapshots of critical system files that can roll back problematic changes, while full image backups clone your entire drive so it can be restored onto new hardware. Creating bootable recovery media (a USB or DVD that can start your computer when the main drive fails) is the safety net that makes recovery actually possible.
Create a system restore point on your computer right now and note how quickly it completes. Then create a full image backup to an external drive using your OS's built-in tool (Windows Backup, Time Machine on Mac). Finally, create a bootable recovery USB so you have the means to restore if your main drive fails.
From your study of backup and data protection, you know how to save files to external drives or cloud storage. System backup extends that logic to an entirely different level: instead of preserving individual documents, it preserves the entire working state of your computer — the operating system, every installed application, all settings and preferences, and your personal files as a unified whole. The practical difference is what happens when catastrophe strikes. If only your files are backed up and your hard drive fails, you still face hours (or days) of reinstalling the OS, downloading and configuring every application, and hunting down license keys. A system image backup eliminates all of that: the full disk can be restored to a new drive in roughly the same time it takes to copy the data.
The hierarchy of system backup tools moves from light to heavy. A restore point (Windows) or Time Machine snapshot (Mac) captures only system-critical files — registry entries, drivers, system libraries — and can roll back a bad software update or driver install in minutes. It is not a disaster-recovery tool; your personal files are untouched and unprotected by it. A full system image — created by Windows Backup and Restore, Macrium Reflect, or similar tools — clones your entire drive sector by sector. Restoring it requires starting from outside the failed drive, which is why the third element matters enormously: bootable recovery media. A recovery USB created in advance is the tool that lets you start your computer when the main drive has failed and initiate the restoration. Without it, even a perfect system image is inaccessible.
The professional standard is the 3-2-1 rule: keep at least 3 copies of your data, on at least 2 different media types, with at least 1 copy offsite. Two copies on the same external drive shelf are both destroyed in a fire or theft. Onsite plus cloud satisfies this neatly: a local image for fast recovery, and an offsite copy for protection against physical disasters. Services like Backblaze or cloud image tools handle the offsite requirement continuously and automatically.
The most important habit to build is testing restoration — not just creating backups. A backup that has never been tested is an assumption, not a guarantee. Boot from your recovery USB to confirm it works. Restore a single folder from your image to verify the backup is readable. Do this when nothing is broken, so you are not learning the process under stress during an actual emergency. The goal of system backup is not to create files on an external drive; it is to compress the distance between catastrophe and a fully functional computer.
No topics depend on this one yet.