Chapter 18 — Backups in practice
Lesson map
Lesson 18 published. Map, example, EX052.
flowchart TD
N0["Learning outcomes"]
N1["18.1 Coverage"]
N2["18.2 Restore tests"]
N3["18.3 Ransomware protection"]
N4["18.4 Cloud supplier backups"]
N0 --> N1 --> N2 --> N3 --> N4
N4 --> EX["Worked example"]
EX --> Q["Exercise EX052"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["18.1 Coverage"]
N2["18.2 Restore tests"]
N3["18.3 Ransomware protection"]
N4["18.4 Cloud supplier backups"]
N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX052"]
[Learning outcomes]
|
v
[18.1 Coverage]
|
v
[18.2 Restore tests]
|
v
[18.3 Ransomware protection]
|
v
[18.4 Cloud supplier backups]
|
v
[Worked example] --> [Exercise EX052]
Learning outcomes
You will (1) check backup coverage; (2) test restores; (3) protect backups from ransomware.
18.1 Coverage
Jamal lists what Riverbend backs up: the file server nightly and the booking system by its cloud supplier. Camera footage and the finance computer's local files are not backed up. He discusses each with the IT manager. Camera footage is kept for thirty days on recorders and is acceptable without backup. Finance local files should move to the file server. Ms. Grant notes that knowing what is not backed up matters as much as knowing what is. He records the decisions in the backup plan.
18.2 Restore tests
Jamal tests restores monthly. He restores a sample of files to a separate folder and compares their fingerprints with the originals using Python's hashlib module. In one test, a folder fails to restore because the backup job excluded it after a folder rename. He fixes the job and retests. He learns that backup jobs can report success while silently missing data, so restores are the only proof. He records each test in a log with the files checked, the result and any fix, so the IT manager can show insurers that restores are tested.
18.3 Ransomware protection
The file server backups are stored on a device reachable from the network with the same administrator password. Ransomware could encrypt both. Jamal recommends a second copy with a cloud backup service that keeps versions for thirty days and cannot be deleted by Riverbend's normal administrator accounts. The IT manager arranges it. Ms. Grant notes that backups must assume attackers will look for them. He also separates the backup device's administrator password from the main administrator account and stores it in the password manager with restricted access.
18.4 Cloud supplier backups
Jamal checks the booking system contract for backup terms. The supplier backs up daily and keeps copies for fourteen days, but Riverbend has never requested a restore. Jamal asks the supplier to demonstrate a restore of a test record. The supplier does so within a day. He records the result and adds a yearly demonstration request to the calendar. He also asks how long a full restore of the booking system would take, and the supplier estimates several hours. The IT manager shares this with centre managers, who agree that paper sign-in sheets would be used meanwhile.
Worked example
Jamal lists backup coverage and gaps, finds a renamed folder excluded through monthly restore tests, adds an undeletable cloud copy and asks the booking supplier to demonstrate a restore.
Synthetic case. Backups are synthetic.
Errors and limits
A backup job that reports success may still be missing data.
Exercises
- EX052 — Moved files. What should happen to finance local files? Rubric: 3 = move to the file server;; 2 = partly correct;; 1 = vague;; 0 = none.
- EX053 — Restore failure. Why did a folder fail to restore? Rubric: 3 = excluded after a rename;; 2 = partly correct;; 1 = vague;; 0 = none.
- EX054 — Supplier retention. How long does the booking supplier keep backups? Rubric: 3 = fourteen days;; 2 = partly correct;; 1 = wrong;; 0 = none.
Continue studying — lesson 18 (chapter 18 of 30)
← Chapter 17 · Course chapter index · Chapter 19 →
Continue to the next authored lesson.