Skip to main content

Backup and Archiving Practices

Because the only unrecoverable mistake is losing the file

In This Lesson

Why This Is Non-Negotiable

Every technique in this course can be redone — except recovering a file that no longer exists. Drives fail, laptops are stolen, ransomware strikes, and a single wrong click deletes a folder. For a photographer or designer, the images are the work. A backup habit is the cheapest insurance you will ever buy, and the one most people only value the day after they needed it.

🎨 An Analogy

Backups are like a seatbelt: an inconvenience you'll wear for years and hope never to need — but the one time you do, nothing else matters.

The 3-2-1 Rule

The industry-standard strategy, simple enough to actually follow:

  • 3 copies of your data (the working copy plus two backups).
  • 2 different media/devices (e.g. your computer and an external drive).
  • 1 copy off-site (cloud, or a drive kept elsewhere) to survive fire, theft, or flood.
flowchart LR W[Working copy on computer] --> B1[Local backup: external drive] W --> B2[Off-site backup: cloud] B1 --> S[Survives a drive failure] B2 --> D[Survives fire or theft]

Three copies, two media, one off-site — survives almost any single disaster.

What to Back Up

Not everything is equally precious — prioritize what you cannot recreate:

PriorityFilesRecreatable?
CriticalOriginal captures, layered XCF mastersNo — irreplaceable
ImportantYour GIMP profile: templates, presets, brushes, palettesPainful to rebuild
LowerExports (JPEG/PNG)Yes — regenerate from the master

💡 Don't Forget Your GIMP Profile

Back up the GIMP user folder (find it under Edit → Preferences → Folders) alongside your images. It holds every custom template, preset, brush, and palette from Monday's lesson — hours of setup you'd otherwise lose.

Backup vs. Archive

They sound alike but serve different needs:

  • Backup — a working safety net of active files, kept current and quick to restore. Its job is recovery from failure.
  • Archive — long-term storage of finished projects you rarely touch, moved off your working drive to free space. Its job is preservation.

When a project closes, archive its originals and final XCF (well-labeled, per your naming convention) to long-term storage, and remove it from the active working area to keep that lean.

Automate and Verify

  • Automate — a backup you must remember to run is a backup you'll forget. Use your OS's built-in tool (Time Machine, File History) or a cloud sync so it happens without you.
  • Verify — periodically open a backed-up file to confirm the backup actually works. An untested backup is only a hope.
  • Off-site matters — a second drive next to the first is useless in a fire. Keep one copy elsewhere or in the cloud.

⚠️ Sync Is Not Backup

A folder that syncs (Dropbox, Drive) instantly propagates your mistakes — delete or corrupt a file and the sync dutifully deletes/corrupts every copy. True backup keeps version history so you can roll back. Prefer tools that retain old versions.

Practice Activities

  1. Audit your risk. List where your only copy of each critical file currently lives. Any single points of failure?
  2. Set up 3-2-1. Add one local backup drive and one cloud/off-site copy for your image folders and GIMP profile.
  3. Test a restore. Recover a file from your backup and open it to confirm the backup is real.

Summary

✅ Key Takeaways

  • Lost files are the one unrecoverable mistake — backup is non-negotiable.
  • Follow the 3-2-1 rule: three copies, two media, one off-site.
  • Prioritize originals, XCF masters, and your GIMP profile; exports are recreatable.
  • Distinguish an active backup from long-term archiving of finished work.
  • Automate, keep version history, and verify — sync alone is not backup.

➡️ What's Next

Wednesday opens the door to automation with Script-Fu and Python-Fu Basics.

Additional Resources