Enable Timeshift Snapshots on Linux Mint: RSYNC vs BTRFS Mode Decision Guide

The Decision: Choose RSYNC Mode for Standard Mint Installs

Linux Mint's Update Manager prompts you to configure Timeshift before applying updates. This is not optional hygiene—it's the supported rollback path when a kernel, driver, or library update breaks boot or networking. The decision is binary: if your root filesystem is ext4 (the default), use RSYNC mode. If you installed on a BTRFS root with @ and @home subvolumes, use BTRFS mode. Mint's installer does not create that subvolume layout by default, so RSYNC mode covers virtually every out-of-the-box installation.

Constraints That Drive the Choice

• Filesystem: ext4 → RSYNC; BTRFS with Mint's expected subvolumes → BTRFS. Any other layout (LVM, ZFS, BTRFS without @/@home) falls back to RSYNC.
• Snapshot storage: RSYNC snapshots live on the same partition by default. On a 256 GB SSD with 20 GB free, 3–5 daily snapshots plus one weekly is sustainable. Below 15 GB free, reduce retention or move the snapshot directory to a second drive.
• Scope: Timeshift snapshots system files only (/etc, /usr, /var, /opt, /root). User home directories are excluded by design. Personal files need Mint's Backup Tool or another backup solution.
• Recovery environment: A working Mint live USB is required for rollback when the system won't boot. Keep one current.

Mode Comparison

Factor	RSYNC Mode (ext4, default)	BTRFS Mode
Filesystem requirement	Any (ext4, xfs, etc.)	BTRFS root with @ and @home subvolumes
Snapshot mechanism	Hard-linked incremental copies via rsync	Native BTRFS subvolume snapshots (copy-on-write)
First snapshot size	~size of included system directories	Near-zero (metadata only)
Subsequent snapshot overhead	Only changed files consume new blocks	Only changed blocks consume new space
Bootloader handling	Restores GRUB config; may need grub-install after rollback	Restores subvolume state; GRUB usually consistent
Live USB restore	Supported (mount target, run Timeshift)	Supported (mount subvolumes, run Timeshift)
Mint installer default	Yes	No (requires manual partitioning)

Trade-offs

RSYNC Mode

Pros: Works on any filesystem, no reinstall needed, transparent hard-link deduplication, mature tooling. Cons: First snapshot is large; restoring many small files is slower than BTRFS copy-on-write; snapshots on the same disk offer no protection against hardware failure.

BTRFS Mode

Pros: Near-instant snapshots, minimal space for unchanged data, atomic rollback. Cons: Requires specific subvolume layout at install time; Mint's graphical installer does not create it; BTRFS tooling (scrub, balance) adds maintenance; kernel/BTRFS version mismatches between live USB and installed system can complicate restore.

Bottom line: Unless you deliberately partitioned for BTRFS with @/@home during install, select RSYNC mode and move on.

Concrete Setup: RSYNC Mode on ext4

1. Launch Timeshift and Select Mode

# Run from application menu or terminal
sudo timeshift-gtk

In the wizard: choose RSYNC (not BTRFS). Snapshot location defaults to the root partition (/timeshift). If you have a second internal drive mounted at /mnt/backup, select it instead—this protects against disk failure.

2. Configure Schedule and Retention

Recommended starting profile for a desktop with ≥20 GB free:

• Daily: On, keep 3
• Weekly: On, keep 1
• Monthly: Off
• Boot: Off (adds noise; daily covers it)

Adjust down if df -h / shows <15 GB free after the first snapshot.

3. Verify Exclusions

Open Settings → Filters. Confirm /home is excluded (default). Add /var/cache/apt/archives and /tmp if not already listed—they bloat snapshots without value.

4. Create the Baseline Snapshot

# GUI: click "Create" and wait for completion
# CLI equivalent (run as root):
timeshift --create --comments "Baseline before updates" --tags D

Check space impact:

df -h /
# Expect 2–6 GB used for first snapshot on a typical Mint install
ls -lh /timeshift/snapshots/
# Should show one directory with timestamp

Validation: Controlled Rollback Test

Do this once before you need it.

1. Snapshot: Create a manual snapshot tagged "test-rollback".
2. Mutate: Install a harmless package you can identify later:

   sudo apt update && sudo apt install -y cowsay
   

3. Verify change: which cowsay returns a path; cowsay test works.
4. Restore: Open Timeshift, select the "test-rollback" snapshot, click Restore. Choose target device (usually pre-filled), keep "Reinstall bootloader" checked, start restore. System will prompt for reboot.
5. Confirm rollback: After reboot, run which cowsay (should return nothing) and apt list --installed | grep cowsay (no output).

If the package is gone, the rollback path works. If GRUB fails, boot the live USB, mount the root partition, and run sudo grub-install /dev/sdX (replace sdX with your boot disk) from the live environment.

Live USB Restore Drill

Once a year, boot the Mint live USB, open Timeshift, and verify it detects your snapshots on the target disk. This confirms the restore path works outside the installed OS. No need to actually restore—just confirm visibility.

Limitations and Ongoing Checks

• Not a backup: Deleted files in /home/user are gone forever after a snapshot restore. Pair Timeshift with Mint Backup Tool (mintbackup) or rsync to external media for personal data.
• Disk pressure: Run df -h / after each major update cycle. If free space drops below 10 GB, prune old snapshots in Timeshift or move the snapshot directory.
• Kernel/GRUB edge case: Rolling back across a kernel major version (e.g., 6.8 → 6.11) can leave GRUB pointing to missing initramfs. The "Reinstall bootloader" checkbox during restore handles most cases; if boot fails, live USB + grub-install fixes it.
• BTRFS mode on ext4: Selecting BTRFS mode on an ext4 root fails silently or creates unusable snapshots. Verify mode matches filesystem with findmnt -n -o FSTYPE / before committing.

Quick Verification Checklist

• [ ] Timeshift shows RSYNC mode and correct snapshot location
• [ ] Baseline snapshot created and visible in list
• [ ] df -h / shows acceptable free space after first snapshot
• [ ] Controlled rollback test passes (package installed → snapshot restore → package gone)
• [ ] Live USB detects snapshots on target disk
• [ ] Separate backup for /home configured and tested