On Sun, Aug 9, 2015 at 1:43 PM, Diogene Laerce me_buss777@yahoo.fr wrote:
http://snapper.io/ http://rpm-software-management.github.io/dnf-plugins-extras/snapper.html
The documentation says that snapper supports ext4 but only experimentally, do you have any feedback on the matter ?
It requires LVM thinly provisioned volumes. Proper configuration for snapshots is necessary and I don't know whether the defaults from the installer do that.
Le 08/08/2015 02:52, Chris Murphy a écrit :
The closest it comes is choosing Btrfs for installation (you can use something else for /home if you want). The root subvolume on Btrfs can then be snapshot before you do a dnf update, update the snapshot's copy of fstab, and if things go bad you can change the rootflags=subvol=<subvolname> boot parameter to that of the snapshot name. But this assumes some Btrfs knowledge, which at least is not nearly as esoteric and complicated like the rabbit hole that is LVM thin volume snapshots. But that's also an option if you're at least semi-comfortable with LVM.
I even saw there :
https://wiki.archlinux.org/index.php/Btrfs_-_Tips_and_tricks#Automatic_snaps...
that one can configure automatic snapshots at boot which is not far from what you propose.
I guess this is reproducible on Fedora and that would definitely be my preference.
Seems like it's adaptable for Fedora.
So long as the top level of the file system is not mounted (where all subvolumes and snapshots are located), it's OK to do a conventional backup of the whole system. But if the top level is mounted anywhere not excluded from that backup, the backup will see each snapshot as a completely separate instance of all of that data. So if you have root, and 5 snapshots, a backup will see six root fs's that need to be backed up unless you exclude those snapshots somehow (by not making them available in the mounted hierarchy is easiest).