You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been using zfs_autobackup to create local snapshots for a while (from NVMe drives to a backup dataset on spinning disks) and I'm setting up remote synchronisation now, to make sure my ZFS snapshots are backed up remotely as well.
I have two datasets with the autobackup:local property set:
homes/db/dev-apps-pg15 autobackup:local true local
homes/home autobackup:local true local
And I use this command to create local snapshots to my tank/autobackup dataset. This used to work fine:
/root/.local/bin/zfs-autobackup -v --clear-mountpoint --keep-source="10,15min6h,1h1d,1d1w,1w1m,1m1y,1y5y" --keep-target="10,15min6h,1h1d,1d1w,1w1m,1m1y,1y5y" --snapshot-format "{}-%Y-%m-%d-%H:%M:%S" local tank/autobackup
However, since earlier today this error appears when running that command:
! [Target] STDERR > cannot receive resume stream: kernel modules must be upgraded to receive this stream.
! [Target] Command "zfs recv -u -o canmount=noauto -v -s tank/autobackup/homes/db/dev-apps-pg15" returned exit code 1 (valid codes: [0])
! [Source] homes/db/dev-apps-pg15: FAILED: Last command returned error
Does this happen because of some (unintended) change I made to the datasets or the data in them, or is this a bug?
This is on the latest pre-release version:
I've been using
zfs_autobackup
to create local snapshots for a while (from NVMe drives to a backup dataset on spinning disks) and I'm setting up remote synchronisation now, to make sure my ZFS snapshots are backed up remotely as well.I have two datasets with the
autobackup:local
property set:And I use this command to create local snapshots to my
tank/autobackup
dataset. This used to work fine:However, since earlier today this error appears when running that command:
Does this happen because of some (unintended) change I made to the datasets or the data in them, or is this a bug?
This is on the latest pre-release version:
Here's the "SYNCHRONISING" portion of the output with
--verbose --debug
enabled:The text was updated successfully, but these errors were encountered: