Linux · Storage & Backup

Set up backups and system snapshots before something goes wrong

Linux offers several backup layers that solve different problems — file-level backups for your personal data, and filesystem or system-level snapshots that let you roll back an entire update or configuration change in minutes.

How to open Backup & Snapshots

  1. Take a test snapshot or backup and verify it appears with the expected size and timestamp.
  2. For Timeshift, use the "Restore" preview to confirm which files would be affected before you actually need to use it in an emergency.
  3. Test that backed-up files can genuinely be opened from the backup location, not just that the backup job reported success.

What you should know

  • Timeshift is the most common GUI snapshot tool — supports rsync-based snapshots (any filesystem) or native btrfs snapshots (much faster, near-instant) if your root is on btrfs. Install via `sudo apt install timeshift` / `sudo dnf install timeshift` / `sudo pacman -S timeshift`.
  • Btrfs users can also snapshot manually with `sudo btrfs subvolume snapshot / /.snapshots/pre-update` before a risky change, and many distros (openSUSE, some Fedora spins) auto-snapshot before every package transaction via `snapper`.
  • For personal file backups, `rsync -av --delete /home/user/ /path/to/backup/` is the classic command-line approach; `Deja Dup` (GNOME) or `KBackup` (KDE) provide a GUI with scheduling.
  • Cloud sync tools (Nextcloud client, rclone for most cloud providers) cover offsite backup, but should complement rather than replace a local backup.

A snapshot of your system is not the same as a backup of your personal files — most snapshot tools exclude /home by default, so pair system snapshots with a separate file backup strategy.

Why it matters

The single most common reason people lose confidence updating Linux is fear of an update breaking the system with no way back — a working snapshot setup turns that into a two-minute rollback instead of a reinstall.

Best practices

  • Take a snapshot right before any major update, driver change, or distro upgrade — not just on a schedule.
  • Follow the 3-2-1 rule where practical: at least 3 copies, on 2 different media types, with 1 copy offsite.
  • If using Timeshift with rsync mode, exclude large media directories to keep snapshot size and time manageable.

Common problems and fixes

Snapshot restore doesn't bring back personal files
Expected behavior for most tools by default — check your snapshot tool's include/exclude list and add /home explicitly, or run a separate file backup for personal data.
Btrfs snapshots filling up disk space over time
Old snapshots aren't automatically freed — set a retention policy (Timeshift and snapper both support this) and prune manually with `sudo btrfs subvolume delete` if needed.

Tips and tricks

  • Boot into GRUB and pick a Timeshift/snapper snapshot entry directly (both add boot menu integration on btrfs) to recover a system that won't boot at all, without needing a live USB.

Frequently asked questions

Is Timeshift a full backup solution?

It's a system-recovery tool, not a full backup — it protects against a bad update or config change, but you still need a separate personal-file backup (and ideally an offsite/cloud copy) for real data-loss protection.