search

teejee2008 / timeshift

System restore tool for Linux. Creates filesystem snapshots using rsync+hardlinks, or BTRFS snapshots. Supports scheduled snapshots, multiple backup levels, and exclude filters. Snapshots can be restored while system is running or from Live CD/USB.
GNU Lesser General Public License v3.0
4.69k stars 282 forks source link

support ZFS as snapshot location #417

Open mabod opened 5 years ago

mabod commented 5 years ago

I want to store the snapshots on a ZFS RAID10 or RAIDZ2. But timeshift is not showing these volumes. Although Issue #291 claims that ZFS is supported.

I am using Manjaro Testing with timeshift 19.01-1

defyjoy commented 4 years ago

This has been open for a long long time . Is there update on this ? The above statement is true . IT does not give option neither show the volumes .

mabod commented 4 years ago

No update. Just checked it with timeshift-20.03.r0.gcecd294-1. When I select rsync as the method timeshift is asking me to pick the location of the snapshot and it list the raw devices (my four hard discs) although they are a member of a zfs RAID10.

When I select one of the drives timeshift complains on the console:

selected device: /dev/sda1
E: Failed to mount device '/dev/sdb1' at mount point '/run/timeshift/backup'
E: mount: /run/timeshift/backup: unknown filesystem type 'zfs_member'.

That really scares me. Will that destroy my zfs pool at tsome point?

Instead of showing the single raw devices - which is really dangerous from my point of view - timeshift should only show the zfs datasets on the RAID10 pool.

chudkins commented 4 years ago

I am seeing the same behavior: My zfs members are all shown, except that only one indicates any free space. Attached screenshot shows what I mean.

timeshift_zfs

Expected behavior (or at least, more intuitive) would be to show only the zfs dataset (in my case, "datastore") instead of the raw volumes. I do see that when I select any of the zfs members shown, the radio buttons for all three are turned on. Still, it isn't obvious to me as the user what would happen if I tried to proceed.

I am also on Manjaro, with Timeshift package timeshift-20.03.r8.gad3c01c-1 here.

stellarpower commented 4 years ago

I am admittedly using an out-of-date version, although that is precisely why; I need to backup before I upgrade and don't yet have root on ZFS. Timeshift requires (at least on this version) to have a whole ext4 partition and will place its snapshots in the /timshift directory - is there a specific reason for this? I'd far rather be able to point ot an arbitrary directory and use this instead. Currently I am creating an empty ext4 partition large enough for a full backup (a small "trick" volume did not work as it checks it has enough free space) and bind mounting this to my ZFS dataset I use for Timeshift.