Closed derandiunddasbo closed 1 month ago
As I couldn't solve this issue and didn't find any clue, why this error even happens, I finally gave up on the tool and switched to syncoid. Because of that, I couldn't do any more testing or debugging with my setup, if this issue would be worked on. Thus, I'm closing this issue.
sorry for my late response.
if someone has this issue: try zfs-autobackup v3.3, it has build in guid-checking and will warn you if a common snapshot is incompatioble.
I suspect in your case, something is creating snapshots on both the source and target sides. (maybe a snapshotter cronjob?)
Then zfs-autobackup will incorrectly assume that the snapshots point to the same data, because they have the same name.
I have a strange problem performing backups of a datasets to a locally attached external USB drive.
After running a successful backup for all datasets onto the target drive, when I'm running the next backup only seconds later, literally without touching anything on the source or the target datasets, the backup of one of the datasets is suddenly failing most of the times. In some rare cases, the next run is successful again, but most if the time the backup keeps failing for this one dataset.
For now, the only thing that I could figure out to recover from this error, is to destroy this dataset including snapshots on the target and all "backup-zfs" prefixed snapshots on the source, thus forcing a full backup again for this one dataset.
I'm not a zfs expert and have no clue, what to even look for to find the source of this problem. Why is zfs-autobackup able to perform a successful backup, but is failing with the same command executed literally seconds later, because of a mismatch of the most recent snapshots on the source and the target?
This is the output from a
--debug
run performed immediately after a failed run:These are the snapshots created by zfs-autobackup after a couple of failed runs. Obviously, the command keeps creating snapshots on the source despite the error and then seemingly complaining about the snapshots on the target not being in sync with the source: