Backing up data means creating a copy that can restore the original if the primary version is lost, corrupted, or destroyed. Good backup strategies protect individuals and organisations from hardware failure, ransomware, accidental deletion, and natural disasters — making backup planning a key topic in GCSE computer science.
Why is data backup critical?
Data loss can happen through many routes — none of them rare:
| Threat | How it causes data loss |
|---|---|
| Hardware failure | Hard drives and SSDs die without warning; RAID helps but is not a backup |
| Ransomware | Malware encrypts all data and demands payment; affects all connected drives simultaneously |
| Accidental deletion | A user deletes or overwrites files — including backup files stored on the same device |
| Theft or loss | A stolen laptop or phone takes its data with it |
| Fire, flood, or disaster | Physical destruction of premises can destroy every local copy |
| Software corruption | Bugs, failed updates, or file system errors can corrupt data without any hardware failure |
| Human error | Incorrectly formatted drives, unintended writes, or misconfigured systems |
The rule in data management: it is not if a disk will fail, but when. Backup is insurance against this certainty.
What is a full backup?
A full backup copies every file in the designated scope — every document, database, and configuration file — to the backup destination.
Advantages:
- Simple to restore: one backup set contains everything
- No dependency on previous backups
Disadvantages:
- Slow and storage-intensive: even files that have not changed since last week are copied again
- Cannot be done as frequently because it takes so long
Typical use: taken weekly or monthly, often on a weekend when systems are less busy.
What is an incremental backup?
An incremental backup copies only the files that have changed since the last backup of any type — whether that was a full backup or a previous incremental.
Example timeline:
- Monday: full backup (all files)
- Tuesday: incremental — files changed since Monday
- Wednesday: incremental — files changed since Tuesday
- Thursday: incremental — files changed since Wednesday
Advantages:
- Very fast and storage-efficient: only changed files are copied
- Can be run daily or even hourly
Disadvantage:
- Restoring is complex: you must apply the full backup, then every incremental in order. A Wednesday restore requires Monday's full + Tuesday's incremental + Wednesday's incremental.
What is a differential backup?
A differential backup copies all files changed since the last full backup — not since the last backup of any type.
Example timeline:
- Monday: full backup (all files)
- Tuesday: differential — files changed since Monday
- Wednesday: differential — files changed since Monday (includes everything Tuesday had, plus Wednesday's changes)
- Thursday: differential — files changed since Monday
Advantages:
- Faster to restore than incremental: only two sets needed (full + latest differential)
- Faster to create than a full backup
Disadvantage:
- Grows larger each day as more files accumulate since the last full backup
Comparing the three backup types
| Feature | Full | Incremental | Differential |
|---|---|---|---|
| What is copied | Everything | Changes since last backup | Changes since last full |
| Backup speed | Slow | Fastest | Moderate |
| Storage space | Most | Least | Moderate |
| Restore speed | Fastest | Slowest | Moderate |
| Restore complexity | Simple (one set) | Complex (full + all incrementals) | Simple (full + latest diff) |
In practice, many organisations use a combined strategy: full backup once a week, incremental backups every day, and keep several weeks of history.
What is the 3-2-1 backup rule?
The 3-2-1 rule is a widely adopted guideline for backup resilience:
- 3 copies of the data (the original plus two backups)
- 2 different storage media (e.g. an internal hard drive and an external USB drive)
- 1 copy stored off-site or in the cloud (protecting against fire, flood, or theft at the primary location)
Example for a school:
- Original data on the school's server (copy 1)
- Daily backup to a NAS (Network Attached Storage) in the server room (copy 2, different medium)
- Weekly encrypted backup uploaded to a cloud service (copy 3, off-site)
The 3-2-1 rule ensures that no single failure — drive death, fire, or ransomware — can destroy all copies simultaneously.
What is a recovery procedure, and why must it be tested?
A backup is worthless if you cannot restore from it. A recovery procedure is a documented, step-by-step plan for restoring data from backup when the primary system fails.
Why recovery must be tested regularly:
- Backup files may be corrupted without anyone noticing until they try to restore
- Restoration software or hardware may no longer be compatible
- Backup jobs may fail silently — logs should be checked routinely
- Staff responsible for recovery may be unavailable; the procedure must be understandable by others
Industry rule: a backup that has never been tested is not a backup — it is a hope.
Recovery testing typically involves restoring a sample of files to a test environment and verifying they are complete and uncorrupted. Some organisations perform a full disaster recovery drill annually.
Frequently asked questions
Is RAID a backup solution?
No. RAID (Redundant Array of Independent Disks) protects against hardware failure — if one drive in a RAID 1 or RAID 5 array dies, data is not lost. But RAID does not protect against ransomware (which encrypts all drives simultaneously), accidental deletion (the deleted file disappears from all mirrors), or fire (all drives are in the same machine). RAID and backups serve complementary but different purposes: RAID provides availability; backups provide recoverability.
What does "Recovery Point Objective" mean?
The Recovery Point Objective (RPO) is the maximum acceptable data loss measured in time — how old can the restored backup be? An organisation that backs up daily has an RPO of up to 24 hours: in the worst case, a full day's work since the last backup could be lost. An RPO of one hour requires backups every hour. The lower the RPO, the more frequently backups must be taken, and the higher the cost.
What is the difference between a backup and an archive?
A backup is a copy of current data, intended to be restored if the original is lost. Archives go out of date as new backups are taken. An archive is a long-term, intentionally preserved copy — for example, keeping seven years of financial records as required by law. Archived data is not expected to change; backup data reflects the current state of the system. Both serve important but distinct purposes.
Should individuals back up their personal data?
Absolutely. Individual data loss — losing holiday photos, coursework, or personal records — can be permanent. For individuals, a practical 3-2-1 strategy is: data on the computer (copy 1), an external drive at home (copy 2, different medium), and a cloud service such as Google Drive or iCloud (copy 3, off-site). Cloud services also offer versioning — the ability to retrieve earlier versions of a file — which protects against accidental overwrites.
Need to understand data management and system security for your GCSE? Professor Turing at aitutors.me makes every concept clear with real-world examples.