How to Protect Schoolwork From Laptop Failure

Ask one question:

If this laptop vanished right now, what could not be recreated?

That list is the real backup priority.

For a student, it may include much more than the Documents folder.

Inventory the irreplaceable work

Check for:

• current assignments;
• notes;
• research PDFs;
• annotations;
• code;
• creative projects;
• thesis or capstone work;
• lab data;
• photographs;
• scanned paperwork;
• local email or downloads;
• recovery keys.

Do not spend the same effort protecting replaceable software installers and unique research data.

Use the 3-2-1 idea as a practical model

CISA backup guidance commonly describes a 3-2-1 pattern:

• three copies;
• two different media types;
• one copy offsite.

For a student, a practical version might be:

1. working copy on the laptop;
2. automatically synchronized off-device copy;
3. independent external or separate backup.

The exact tools matter less than avoiding one single failure path.

Sync helps, but sync is not always backup

Cloud synchronization is extremely useful.

It can also synchronize mistakes.

Depending on the service, a deletion, overwrite or ransomware-encrypted file may propagate to the synchronized copy.

Version history and recycle-bin features can help.

Important work still benefits from another independent recovery point.

Automate the routine

A backup system that depends on remembering every Friday is fragile.

Automate what you can:

• sync active coursework;
• schedule external backups;
• use version history;
• keep important repositories pushed to a remote.

Then occasionally verify that the automation is still running.

Git is version control, not automatically complete backup

Git is excellent for code and text projects.

It only protects what has actually been committed and pushed to another repository.

It may not contain:

• datasets;
• build artifacts you actually need;
• local configuration;
• large files;
• secrets;
• notes outside the repository.

Use Git for the job it does well and back up the rest appropriately.

Keep school-account lifecycle in mind

A university-managed account is controlled by the university.

Access can change after graduation or separation.

ATSU's KCOM guidance, for example, warns that provided Microsoft 365 access ends after graduation.

Do not leave the only copy of personally important work in an account you will not control forever.

Before leaving school, export material you are allowed to keep.

Restricted academic data needs different handling

Do not copy regulated or institution-controlled data to a personal USB drive or consumer cloud account just because it is convenient.

Research, clinical, FERPA, HIPAA or employer-controlled information may have specific storage rules.

Follow the course, lab and institutional policy.

The correct backup destination depends on the data.

Disconnect some backups

An external drive permanently connected to the laptop can be reached by some of the same failures that affect the laptop.

A disconnected backup can provide stronger separation from:

• malware;
• accidental deletion;
• electrical damage;
• account compromise.

How often to connect it depends on how much recent work you can tolerate losing.

Test restoration

A backup job reporting “success” is not enough.

Periodically:

1. restore a sample file;
2. open it;
3. restore an older version;
4. verify backup credentials;
5. confirm the external drive is readable.

The goal is recovery, not backup activity.

Have a finals-week failure plan

If the laptop dies near a deadline:

• stop risky repeated attempts on a failing drive;
• use a campus or public computer;
• retrieve the backup;
• notify the instructor early if needed;
• repair or replace the laptop separately.

The backup should turn hardware failure into an inconvenience instead of a catastrophe.

For the hardware decision, see Repair or Replace? A Kirksville Student’s Guide to a Failing Laptop.

For used replacement hardware, see Buying a Low-Cost Used or Refurbished Computer in Kirksville.