Linux

Well having a dedicated /home partition is the very minimum and pretty much default.

If you are interested in having a backup/restore solution for your system you are looking for BTRFS which uses sub volumes instead of primary partitions and is compatible with snapshot tools, those tools being Timeshift and Snapper.

I do think Snapper is the superior solution however it's also more complex to set up and requires significantly more prep work. Imo totally worth it.

I currently use it on my main machine Debian with BTRFS and Snapper and couldn't be happier.

On servers I like to have /var on its own partition. Partially as a habit from the olden days of using FreeBSD in the 90's, but also because that means that / will mostly be left with things that don't really change. I've had to clean out clogged up / too many times. So in effect, my partion schema for a typical production server looks like this:

/ ext4
/local xfs
/global usually beegfs or nfs, but sometimes a local xfs.
/var ext4
/home ext4

Btrfs snapshots are great! All my filesystem is Btrfs, with subvolumes for root, home and var.

I'm using the Fedora immutable distros on many computers, it's great to be able to boot into a previous version of the system if issues arise. Not that issues arise, since most packages are installed as Flatpaks, in a toolbox or in a container. Makes the systems nearly unbrickable.

Nothing, I just corupted my hard drive with all my college work for tomorrow and im trying to save them, im feeling so stupid rn, im nothing but a failure at this point

Thanks for all your comments, a lot of interesting things here.

I went with BtrFS with Timeshift. Seems to have improved in terms of performance a lot that I barely noticed any difference compared to the previous installation with Ext4, if any at all.

Unfortunately the current Ubuntu 23.10 installer doesn't properly set btrfs subvolumes correctly for @ and @home and instead instead just throws the entire OS at the root of the FS, making it incompatible with Timeshift and causing FS snapshots to live in the Linux directories, which in turn would cause future snapshots to contain snapshots, not great...

Fortunately migrating to a subvolume layout is possible although it was quite painful following this outdated and a bit not well written post https://www.reddit.com/r/btrfs/s/qWi84tGJam

After successfully installing the system and setting up btrfs layouts and Timeshift, I created the first system snapshot and I feel extremely confident about this solid system.

Thanks again for sharing your experience!

Besides btrfs, there are immutable distros like fedora silverblue. The system doesn't update when something goes wrong during the update and you can roll back if it updated.

It is a bit more difficult to handle and understand, imo, for a new linux user if the user wants to tinker with the system.

I image the whole system to a recovery image using Veeam. Partitions and file systems make no difference.

The new fad is immutable distros as I see more and more. Each major distro seems to have a flavor that is immutable. You are not specific about your needs/use case though

I just have a different partition for /home. For snapshots, you could set a partition up as btrfs and use btrfs snapshots

Wing everything without backups

Right now I'm using Garuda Linux, it takes a snapshot during major updates. Easily restored if something breaks.

Time shift saved my but a time or two in the past.

My strategy has always been to separate what should be persistent from what shouldn't be.

On every system I deploy for home or work, I have a tree similar to below

/storage/[local/remote]/[where it is, enclosure, backplane,etc]/[what it is]

E.g

/storage/local/e1/raid/r6a/[this is my mount point] /storage/remote/nfs4/oldserver/[this is my mount point]

I then build all of my workflows off of the assumptions that things go there. Docker containers have a subdirectory in r6a for persistent volumes, etc

Even my containers themselves have a /storage/remote/persistent that I symlink anything to that I care about.

On the desktop side, I tend to physically just mount a second drive or a second partition as a subdirectory of /storage. That way my assumption can always be safe in that if it's a subdirectory of a mount, my data is safe. If it's not, it isn't. It's also nonstandard, so I can be relatively certain I won't have conflicts between different distributions.

The main issue I have with submounting system directories like /home is that applications tend to put junk there, and old junk might not be compatible with a newer version of, or different distro. It can make for more effort than it's worth

Partitioning doesn't affect backups. Any modern system supports both full images and file-level backups, so even if you take a whole disk image, you can just restore /home if that's what you want.

I would just use whatever filesystem is the default for your distro. For the root partition, usually that's ext4. That's a perfectly good default.

For years I used ext4 and backuped on an external HD/SSD using rsync.

For a couple of months now I redid a test setup with btrfs (and luks), I have a root, home, var, swap subvolumes. I'm using Timeshift for backup, I think I need to format a new external SSD as btrfs too to backup the snapshot.

IIRC in MX Linux, you can create USB bootable snapshot of your system, so a full setup copy of your system, in case of hard crash.

I only have three partitions, all ext4:

• /dev/sda1 mounted as / - if necessary I wipe it out, reinstall my junk and call it a day. The only non-default things there are a few /etc files but I got a manual backup of the ones that matter. It's in the SSD to access is really fast.
• /dev/sdb1 mounted as /home - that's my precious, for files that are personal and/or impossible to replace. Kept as small as possible so I can mirror it into a USB stick. It's in the HDD, right at the start so access is fast.
• /dev/sdb2 mounted as /storage - originally I created this partition to bulk store my anime series, music, etc. so I could broadcast them through SMB across my house. If I lose those files I'll probably be pissed, but they can be recovered with some sweat, blood, and torrents. Access speed is not that big of a concern for those files.

I'm actually considering to create a fourth partition. See, the /storage partition has 1.6 TB, so I created a /storage/binarios subdir in it so I can install a few programs (mostly games)... that's just /opt reinvented poorly, might as well promote it to its own partition.

BTRFS snapshots for sure. Avoid Ext4 at all costs, unreliable and very susceptible to power losses. But frankly I don't even care, all my data is synced with Syncthing so if things go wrong I'll simply install a clean OS and sync the data back.

Never had a backup system, but then again I haven't used Linux that much. Though considering installing Debian again. Last time I looked at btrfs which seemed dope but there was something weird about it which made me ditch it. Maybe it was that I don't know that much about Linux and configuring automatic backups seemed difficult.

I use NixOS & Home Manager. My config is in git, and I use an ephemeral setup with ZFS & tmpfs:

Mount layout:

/		 tmpfs  
├─/boot /dev/sda1  FAT32 EFI system partition
├─/nix	 rpool/local/nix ZFS partition
├─/home/persist rpool/safe/home ZFS partition
└─/persist	 rpool/safe/persist ZFS partition

ZFS partitions under rpool/safe/ get backed up, the rest don't need to be. Everything else can be rebuilt (and most of it gets re-created at boot anyway, since / and /home are tmpfs).

What I do nowadays is to have Timeshift daily backups in case something breaks the system and the Ubuntu backup application doing daily backups of my home to my NAS. I don't have a separate home partition although this is often recommended.

This setup saved me once, but I haven't needed it for almost 2 years now.

500 MiB ESP mounted at /efi
Swap equal to my RAM at /home/swapfile
Root equal to 25% of my disk, formatted with btrfs with auto snapshots.
Home takes the rest of my disk, formatted with btrfs WITHOUT AUTO SNAPSHOTS, so swap works.

I have my EFI boot partition with 512M on /boot, zram instead of swap, then a whole lot of btrfs subvolumes, with RAID across several disks. I do a lot of snapshotting, and auto-snapshotting, but thats mostly for local rollback. I only btrfs-send to a machine on the LAN. For my real backups I use Restic, sending that data to a number of places.

I simply backup the /home folder, where the important files are with duplicity on my home server with ftp once a week, keeping records of the last 6 months. But as that only restores the home folder i also take a snapshot (which takes way more disk space) every month with timeshift too, which stays on the pc. Would be great if i could take complete snapshots via ftp just like with duplicity, but timeshift doesn't do that.

Use Virtmanager, its native on the Kernel (KVM) and doesnt need weird Kernel modifications.

So Ubuntu is really old regarding this. The solution you are looking for is BTRFS, standard on Fedora and Opensuse. It allows snapshots (that both systems automatically create afaik), and this is a specific capability of that filesystem, as these snapshots can be created while using it.

Its really powerful and somewhat magic, as you see no performance lack.

Isolating your home, maybe. Isolating /var could also be nice if you use Flatpaks.

Or just get an immutable System, if you need weird packages use Distrobox/Toolbox, if you want system mods try Ublue.it or layer/remove a few packages, and be happy with Flatpaks for the rest.

To answer your question, Opensuse and Fedora do the snapshots automatically. Just enable offline updates to use this feature more reliably (afaik).

I personally broke Linux Mint, Kubuntu, KDE Neon and Fedora KDE, so I switched to Kinoite.