Week 16 · lesson
Lesson 2: Backup, Safety, and Environmental Controls
Core path: 42 minutes
A backup that has never been tested is a hope, not proven recovery.
A repair performed unsafely is not successful support either.
Today we connect recovery, personal/equipment safety, and environmental control because all three protect system availability.
Backup types solve different problems
Full backup
Copies the complete selected data set for that backup job.
Strength: straightforward restore baseline.
Tradeoff: usually takes more storage/time than smaller change-only backups.
Incremental backup
Copies data changed since the most recent backup in the chain.
Strength: smaller/faster backup jobs.
Tradeoff: recovery may depend on the full backup plus multiple incrementals.
Differential backup
Copies changes since the last full backup.
Strength: recovery usually needs the full plus the most recent differential.
Tradeoff: differential jobs generally grow until the next full backup.
Synthetic full
A backup system creates a new full-like backup from existing backup data without rereading every source file in the same way as a traditional full.
The implementation depends on the backup platform. At A+ depth, recognize its purpose rather than memorizing one vendor workflow.
Recovery location matters
Recovery can restore data:
- in place / overwrite the original location; or
- to an alternative location for validation, comparison, or safer recovery.
Always identify whether overwriting could destroy evidence or a newer copy.
Rotation and resilience
Recognize:
- onsite vs offsite copies;
- grandfather-father-son (GFS) rotation concepts;
- the 3-2-1 principle: three copies, two different media/storage systems, one copy offsite or isolated from the primary failure domain.
A backup stored only on the same failed laptop is not an independent recovery copy.
Test the restore
A successful backup job status does not prove a usable restore.
Verification can include:
- confirm backup completed;
- choose a safe test file/data set;
- restore to an approved location;
- open/validate the restored data;
- document the date/result;
- investigate failures before claiming recovery readiness.
Safety is part of the ticket
Common procedures include:
- ESD strap and mat use where appropriate;
- equipment grounding;
- antistatic bags for components;
- proper component handling/storage;
- cable management;
- disconnecting power before PC repair;
- safe lifting technique;
- fire-safety awareness;
- safety goggles or air-filter mask when the task/environment requires PPE;
- compliance with applicable workplace/government requirements.
Do not perform work you are not trained or authorized to perform.
Environmental controls protect hardware
Disposal
Follow approved procedures for:
- batteries;
- toner;
- electronics/assets;
- other materials covered by safety/environmental documentation such as SDS/MSDS guidance.
Do not place swollen lithium batteries or toner waste into ordinary classroom trash because it is convenient.
Power quality
Power problems include:
- surge: temporary high voltage;
- brownout: sustained/reduced voltage;
- blackout: loss of utility power.
Controls can include surge suppression and an uninterruptible power supply (UPS), depending on equipment and requirements.
A UPS is not unlimited runtime. It provides bounded power continuity and/or safe shutdown opportunity depending on design.
Temperature, humidity, ventilation
Equipment placement matters. Check:
- airflow;
- room/equipment temperature;
- humidity awareness;
- blocked vents;
- dust buildup;
- safe cleaning method.
Compressed air and vacuums can have device-specific safety/ESD considerations. Follow the approved procedure rather than improvising.
Lab: recovery and environment plan
Scenario:
A small office has one receptionist workstation containing important local files. It sits beneath a desk beside a space heater. The user copies the files once a month to a USB drive stored in the same desk drawer. No restore has ever been tested.
Create a plan with:
current risks:
backup type/frequency:
independent/offsite copy:
restore test:
UPS/surge requirement:
placement/temperature concern:
cable/ESD/service safety:
media disposal procedure:
verification evidence:
Evidence checkpoint
A strong plan protects against both data loss and the technician accidentally creating a new safety or availability problem while trying to help.
Visual reference
See the system before you troubleshoot it
Professional IT work is a chain of evidence: request, authorization, baseline, controlled change, verification, documentation, and escalation.
Use it for: Make operational procedure artifacts visible before integrated technician scenarios.
Read it. Prove it.