Administrator: Add English DGB 4 translation

2026-09-11T18:09:06Z

Add English DGB 4 translation

Neue Seite

{{DISPLAYTITLE:DGB 4: Backups and Data Recovery}}
← [[DGB 4. Klasse/en|Digital Literacy – Year 4]]

A backup is useful only if important data can actually be restored when the original is lost,
damaged or encrypted. Students therefore move beyond the idea of 'having a copy' and learn to
select important data, choose suitable storage locations, perform backups and test recovery.

== Curriculum reference ==

{| class="wikitable"
! Area !! Classification
|-
| '''Competence area''' || Information
|-
| '''Perspectives''' || T, I
|-
| '''Focus''' || Performing backups and data recovery
|-
| '''Competence''' || Plan and carry out backups, restore data and evaluate whether a backup strategy is actually reliable.
|}

== Learning objectives ==

Students can:

* explain why backups are necessary;
* distinguish full, incremental and differential backup concepts at a basic level;
* compare local, external and cloud-based storage locations;
* plan a backup routine for school and personal data;
* perform a backup using an approved method;
* restore selected files from a backup;
* verify backup completeness and readability;
* identify typical errors such as keeping the only backup permanently attached;
* apply the basic idea of multiple copies and separate locations;
* create a realistic recovery plan.

== Learning content ==

=== Why backups are necessary ===

Files can be lost through hardware failure, accidental deletion, theft, malware, damaged
storage or account problems. Synchronisation alone is not always a backup because deletions
and unwanted changes can also synchronise.

=== Types of backup ===

A full backup copies all selected data. Incremental and differential approaches reduce repeated
copying by saving changes in different ways. Students need the principle rather than enterprise-
level detail.

=== Storage locations and media ===

Backups can be stored on external drives, network storage or suitable cloud services. A useful
strategy avoids keeping every copy in the same place or under the same account risk.

=== Planning and carrying out backups ===

Decide which data matters, how often it changes, where the copies will be stored and who is
responsible for checking them. A backup schedule should match the value and change rate of the
data.

=== Restoring data ===

Recovery means retrieving data from a backup and checking that the restored files are intact
and usable. A recovery test is the only practical proof that the backup can serve its purpose.

=== Quality checks and common mistakes ===

Common failures include backing up the wrong folders, ignoring error messages, storing
copies on the same device, using an inaccessible account or never testing restoration.

=== A practical backup strategy ===

For important data, keep more than one copy and separate at least one copy from the working
device. The well-known 3-2-1 principle can serve as an orientation: three copies, on two types of
storage, with one copy separated from the primary location.

== Classroom activities ==

=== Analyse data-loss scenarios ===

For several incidents, identify what would be lost and which backup would help.

'''Expected outcome:''' A risk-and-recovery table.

=== Create a backup plan ===

Select important folders, frequency, storage media and responsibility.

'''Expected outcome:''' A personal or school backup plan.

=== Perform a backup ===

Copy a prepared data set using an approved backup method.

'''Expected outcome:''' A completed backup.

=== Practise recovery ===

Delete or move a test file and restore it from the backup.

'''Expected outcome:''' A verified restored file.

=== Compare backup types ===

Compare full, incremental and differential concepts using a simple timeline.

'''Expected outcome:''' A comparison diagram.

=== Find backup mistakes ===

Review fictional backup setups and identify false security or missing copies.

'''Expected outcome:''' A quality checklist.

=== Run an emergency exercise ===

Follow a prepared data-loss scenario from detection to restoration.

'''Expected outcome:''' A recovery log.

=== Develop a routine ===

Create a realistic recurring backup routine for schoolwork.

'''Expected outcome:''' A practical routine.

=== Backup check ===

Explain how you know that a backup is recent, complete and restorable.

'''Expected outcome:''' A short audit.

== Self-check ==

* I can explain the difference between synchronisation and a real backup.
* I can choose suitable data and storage locations.
* I can perform a backup.
* I can restore and verify files.
* I can identify common backup mistakes.
* I have a realistic recovery strategy.

== See also ==

[[DGB 4: Umgang mit Nutzerdaten/en|Handling User Data]]
[[DGB 4: Verschluesselung von Daten/en|Using Encryption Software]]
[[DGB 4: Abstraktionsebenen und Softwareschichten/en|Application Software, System Software and Hardware Layers]]

[[Kategorie:Digitale Grundbildung]]
[[Kategorie:DGB 4]]

DGB 4: Datensicherung und Wiederherstellung/en - Versionsgeschichte

Administrator: Add English DGB 4 translation