Two tools, two jobs
System snapshots capture installed programs and settings so you can undo a bad upgrade. File backups capture your documents and photos. Confusing them is how people “restored” a snapshot and still lost the novel in Documents because it was excluded or never copied off-machine.
On many beginner distros, Timeshift (or the distro’s snapshot UI) handles system restore points. Backups of /home belong in Déjà Dup, Borg, restic, an external drive script, or a cloud client with versioning - pick one and test it.
Snapshot basics
Create a snapshot when the system is healthy - right after a good install and update is perfect. Before big experiments (new desktop environment, beta GPU drivers), take another. Store snapshots on a separate internal partition or external disk when the tool allows. Keeping snapshots only on the same failing SSD is a single point of failure.
Restoring a snapshot can take time and will reboot. Close work first. After restore, update carefully and avoid replaying the exact change that broke things until you know why.
File backup basics
Same 3-2-1 thinking as our Windows-oriented backup guide: multiple copies, more than one media type, one off-site. Encrypt backups that leave the house. Test restore of a few files quarterly.
Versioned backups matter for ransomware and accidental deletes. A bare sync folder that mirrors ransomware encryption is not a strategy - history is.
Shop truth
When a disk is clicking, snapshots will not save you - imaging might. Bring the machine before DIY write tests. We will tell you whether the media is trustworthy enough for an install or only for a recovery attempt.
When to stop DIY
When the stack exceeds DIY - drive failures, dual-boot disasters, locked accounts, or a machine that must be online for work tomorrow - contact CCPCREPAIR in Tahlequah. We do diagnostics with a flat quote after we know what is wrong. Call 918-228-5889 or use the form.
← Linux is easy series · All guides · Book a diagnosticField notes from the shop
At CCPCREPAIR in Tahlequah we see the same pattern repeatedly: people succeed with Linux when they slow down for backups, pick a mainstream distro, and treat the first week as landing the plane - updates, browser, printer - before theming and experimental drivers. They fail when they skip the backup, click through erase-disk options, or paste sudo commands they cannot explain.
Keep a live USB of the same distro in a drawer. It is a recovery tool as much as an installer. When something will not boot, the live session is how you copy files off and read logs without making the problem worse. That habit alone separates calm operators from emergency tickets.
If you share a machine with family, write a one-page note: distro name, username model (not the password), whether the disk is encrypted, and where the backups live. Future you - or a technician - will move faster with that sheet than with a vague memory of a YouTube video from three months ago.
Continue the series in order when you can, but jump ahead if you already know the topic. Every page ends with abort criteria and a path to contact the shop when risk climbs. Linux is easy when honesty about hardware and data comes first.