DatuX
i also have this problem, also see https://github.com/litespeedtech/ols-docker-env/issues/77
Hmm i'm not sure if i already responded to this somewhere? I think this solution is too hackish, i would rather see --select-... options for this. ``` zfs-autobackup -v \...
The only result you get with NOT releasing, is that everyone will just use master. So basically every commit you do is a release now..
well i couldnt think of anything better than to add an --include-received option to overule this behaviour. :) (generally most users want the automatic enabling of --exclude-received, so we let...
updated docs, so this one can be closed https://github.com/psy0rz/zfs_autobackup/wiki/Performance#direct-tcp-network-transfer
closing this, since its essentially fixed via that documentation. zfs-rsync is a different thing.
i've looked into it: It only thins missing datasets that are under the target-path and it only destroys snapshots that are according to the formatting/name of the backup.
will a scrub show this? is there another way to detect this kind of corruption?
i have this problem as well, is there a solution?