Should Linux Mint Timeshift include /home in system snapshots by default?

Answer

On a standard Linux Mint installation, Timeshift should continue to exclude /home by default. The default exclusion keeps snapshots small, speeds up creation and restoration, and keeps personal data separate from system state. Users who want /home in a snapshot can enable the toggle in Settings → Scope without affecting the default behaviour for others.

Why the default stays the same

• Size & speed: A typical /home directory can be 10 – 50 GB. Including it would double snapshot size and double restore time for most users.
• Predictable storage use: System restores should fit comfortably on a single SSD partition. Adding /home risks exceeding available space, especially on machines with limited storage.
• Separation of concerns: System files and user data have different lifecycles. Keeping them apart lets users choose a dedicated backup tool (e.g., Deja‑Dup, rsync, cloud sync) for personal files while relying on Timeshift for OS recovery.
• Btrfs nuances: When using Btrfs snapshots, /home is often a separate subvolume. Including it can interfere with incremental snapshot performance and may require careful subvolume layout.
• User awareness: A change in default behaviour could lead to accidental data loss if users delete snapshots thinking they only contain system data.

When you might want to change the default

If you have a very small /home (under 2 GB) and you rely on Timeshift for a single‑click recovery of all files, you could consider enabling /home permanently. However, this is a personal decision and not a system‑wide recommendation.

Steps to verify and adjust the snapshot scope

1. Check current scope:

   cat /etc/timeshift/timeshift.json | grep -i home
   

   The output shows whether "home": true or false.
2. Test snapshot size:

   # Create a snapshot with /home disabled
   sudo timeshift --create --comments "Test without /home"
   # Note the snapshot size
   ls -lh /timeshift/backup/$(ls /timeshift/backup | tail -1)
   
   # Enable /home and create another snapshot
   sudo timeshift --create --comments "Test with /home" --include-home
   ls -lh /timeshift/backup/$(ls /timeshift/backup | tail -1)
   

3. Restore a snapshot that includes /home (use a test environment if possible). Verify that all files in ~/Documents, ~/Pictures, etc., are present.
4. Check logs:

   grep -i snapshot /var/log/timeshift.log | tail
   

   Look for the scope field to confirm what was backed up.

Diagnostic question for your setup

Do you use Btrfs and have /home mounted as a separate subvolume? If so, the interaction between Timeshift’s rsync mode and Btrfs snapshotting could affect incremental performance, and you might need to adjust your subvolume layout before enabling /home in system snapshots.

Bottom line

Keep the default exclusion of /home to maintain lightweight, predictable system restores. Enable it only when you have a clear need and understand the storage implications.