Using Timeshift in Linux Mint for Safe System Rollbacks
Learn how Linux Mint’s Timeshift tool uses rsync hard links to create system snapshots that let you roll back updates without affecting personal files.
21 Jul 2025, 20:16 UTC

The Problem: A Broken Update
Every Linux Mint user eventually faces the moment when a system upgrade, a new kernel, or a third-party driver leaves the machine unbootable. Instead of reinstalling the whole OS, you want a way to roll back to a known‑good state while keeping your personal files intact.
How Timeshift Creates System Snapshots
Timeshift is the built‑in tool that takes snapshots of the root filesystem using rsync and hard links. The first snapshot copies all selected files. Later snapshots only copy files that have changed; unchanged files are represented by hard links that point to the same data blocks as the previous snapshot. This makes each snapshot appear as a full system backup while only the changed data consumes extra space.
What Timeshift Snapshots Include (and Exclude)
By default Timeshift backs up directories such as /etc, /usr, /var and /boot. The user’s home directory (/home) is excluded because a system rollback should not overwrite personal documents, downloads, or configuration files stored there. This separation means you can restore the OS without risking data loss in your home folder.
Worked Example: Preparing for a Risky Driver Installation
- Open Timeshift from the menu and click Create to take an immediate snapshot of the current stable state.
- Verify that the new snapshot appears in the list with a timestamp and an optional comment (e.g., pre-driver-install).
- Proceed with the driver installation or any system change you consider risky.
- Reboot and test. If the system fails to boot or behaves incorrectly, you have a recovery point.
Restoring from a Live USB: If the installed system will not start, boot a Linux Mint Live USB, launch Timeshift (it is available in the live session), choose Restore, select the snapshot you created, and let Timeshift overwrite the corrupted system files. Your /home remains untouched because it was never part of the snapshot.
Trade‑offs and Limitations
| Aspect | Rsync Mode (default) | BTRFS Mode |
|---|---|---|
| Filesystem requirement | Works on ext4, xfs, etc. | Requires a BTRFS filesystem |
| Snapshot creation speed | Copies only changed files | Near‑instant subvolume snapshot |
| Restore speed | File‑by‑file copy (moderate) | Subvolume swap (fast) |
| Disk usage efficiency | Hard links save space for unchanged files | Copy‑on‑write snapshots |
The rsync approach is not a true block‑level snapshot, so it cannot capture the exact state of open files or databases that are mid‑write. Because /home is excluded, Timeshift is not a substitute for regular data backups; a disk failure will destroy both the live system and the snapshots stored on the same drive. For complete protection, pair Timeshift with a dedicated backup tool for personal data (e.g., Deja Dup or an external rsync script).
Verification and Maintenance
To see what Timeshift has stored, run:
sudo ls -lh /timeshift/snapshots
Each entry is a directory named by date and time. Inside, you will find the replicated root hierarchy. To estimate the unique space used, you can use:
sudo du -sh --hard-links /timeshift
Remember that restoring a snapshot will revert any system‑wide changes made after the snapshot was taken (e.g., new users, modified network settings). Always create a fresh snapshot before major updates if you want to retain the ability to roll back.
0 replies
A thoughtful contribution can make all the difference. Be the first to share one.